Discussion about this post

User's avatar
Jibone's avatar

"If you suspect your private key has been exposed (e.g., you logged in on a sketchy device or shared it by mistake), generate a new key pair immediately. Announce your new npub to your followers from your old account (if you still have access) and migrate over."

This, to me, is one of Nostr's biggest drawbacks. If your key is compromised, there's no recovery mechanism beyond generating a new key pair and manually announcing the change.

I’m not deeply familiar with the development of NIPs, but I hope someone is working on an account abstraction mechanism to improve this.

For example, instead of using my nsec directly (or through a plug-in or signer), I should be able to generate a sub-key for each client or website—one that links back to my original key pair. If a specific client or website gets compromised, I could simply revoke that sub-key without affecting my main identity.

Essentially, this would function like OAuth, but in a decentralized manner where I fully control my identity.

I’m not technical enough to dive into the implementation details, but from a user’s perspective, this would be an incredibly valuable feature—letting me create dedicated keys for different services while keeping my identity intact.

Expand full comment
3 more comments...

No posts

Ready for more?