someone on nostr

Open in Damus

Vitor Pamplona · 187w

Hear me out: A Nostr Service where you can send leaked private keys to: 1. delete everything from those keys everywhere 2. watch for new posts from those keys and delete them as well, forever. The ...

someone @someone 1679072461

1. Set a spare pubk B using secret key A
2. In case the secret key A is stolen, use secret B to publish a special event that says "B is now the secret key replacing A"
3. Clients show a warning that A is stolen and B is the new one. Clients update the follows. Relays can't do much..

8❤️4🤙3

symbsrcool · 187w

Super interesting, hope others comment on the feasibility of this

This. A revoke key. That allows old key to be marked as old a set a new one.

And possibly copy everything from the old key to the new one, including followers and following.

Vitor Pamplona · 187w

What blocks the attacker to go back in time and publish a second pubk B? How do you know which event to trust if you have two of them?

someone · 187w

Couple of solutions could be 1 Relays relaying meta data about when they received it. Means bigger nips. 2 Relays not accepting 'declaration of successor' more than 7 days old. Not sure if this needs a nip.

Vitor Pamplona · 187w

What if you are using the Gossip Model (Auto finding relays) and the attacker gets a hold of your keys, changes your relay to their custom relay and remove those protections?

someone · 187w

I think easiest is to block successor events that are older than 7 days. I could do this on nos.lol with plugin. Anybody can query it then to find the earliest successor event for a given pub.

I get what you're saying and you're right that the problem is people, but you need not only a way to delete your old npub but also claim your new npub, the revoke key could be a password chosen by you, like in bitcoin, you can have your seed phrase+pass. Another option could be social recovery but y...