That was unfortunate. I can't imagine any solution that a bad actor couldn't reverse or make worse.

I think you're going to have to create a duplicate account, move your profile over and employ all of your followers to drop the old account and follow the new one.

You can post from both to give some sort of proof of truth, and the sooner everyone is off the old account and following your new one, the sooner you can pretend it never happened.

Reply to this note

Please Login to reply.

Discussion

Emplore*

Makes sense. All I was concerned with was someone being able to zap or post notes.

#asknostr

Does it make sense to build a kill switch note type that effectively tells relays to block anything related to a specific user id?

The "If I can't have it, no one can" feature.

Something like that would be nice. But it would have to be voluntary. Some people may not want that.

You would have to sign and publish such an event yourself.

In your case, someone else could do it, but all it does is prevent further misuse of a compromised account. There is no putting the cat back in the box anyway.

So if you have your key safe and sound, it's your choice to destroy the account or not. You might do it if you don't want the account anymore, or you may never do it.

If your account is compromised, you can lock it down or let it be used for nefarious reasons. It's up to you but also up to anyone else who has your private key.

Yes, I would use something like that. But I suspect it goes against the overall ethos on Nostr of keeping everything permanent. I'll keep the old account open until I have time to create a new one. I just won't zap with it.

Looks like there's already something brewing in the pipeline.

https://github.com/nostr-protocol/nips/blob/key-invalidation-and-migration/37.md

I knew I saw something in my feed. Thanks for searching. I'm going to watch this to see how it goes.

Got the wallet fixed. Thanks for the help.