Fabian on Nostr: yea I debugged some more and it does actually check if the private key belongs to ...
yea I debugged some more and it does actually check if the private key belongs to that read-only account so that can't be it. I did some DB updates in the past, maybe I missed something related to bunker accounts. Could it be that the "wrong" nsec is the bunker client key?
I think you could try to add existing account again and it should override the wrong keychain data, if that works I don't need to add extra tooling to recover
Published at
2024-10-30 08:50:34Event JSON
{
"id": "37185d3b86266f9c8d1b4432e422a5ecf5a844dd5a200b321dd1ceff7cae44f5",
"pubkey": "9be0be0e64d38a29a9cec9a5c8ef5d873c2bfa5362a4b558da5ff69bc3cbb81e",
"created_at": 1730278234,
"kind": 1,
"tags": [
[
"e",
"799140903b604bc9925069afea1692bbe45213ccacdc8de7ac7a1b0dc77912b4",
"",
"root"
],
[
"e",
"e74810ef31de1076f86e556afa2a7b7da7b9faaa7fda76f2e9001ff295f54373",
"",
"reply"
],
[
"p",
"fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52"
],
[
"p",
"9be0be0e64d38a29a9cec9a5c8ef5d873c2bfa5362a4b558da5ff69bc3cbb81e"
],
[
"client",
"Nostur",
"31990:9be0be0fc079548233231614e4e1efc9f28b0db398011efeecf05fe570e5dd33:1685868693432"
]
],
"content": "yea I debugged some more and it does actually check if the private key belongs to that read-only account so that can't be it. I did some DB updates in the past, maybe I missed something related to bunker accounts. Could it be that the \"wrong\" nsec is the bunker client key?\n\nI think you could try to add existing account again and it should override the wrong keychain data, if that works I don't need to add extra tooling to recover",
"sig": "5303b53c3ca997811880b9ca9c09c3d546deb3f262fe4eabb9a8512dabe3b11c928ce067a395401c2368939b598212e26e94c2fbbc64c5f3eefda4cffd13f305"
}
