It should be possible to have key rotation right? Something like changing your nsec every now and then.
One of the biggest technical hurdles for Nostr is finding a way sign events on web apps without browser extensions and without sharing the nsec with the web.
The browser is your enemy...
As soon as there is any meaningful growth in user base, let's say the next adoption cycle "and nsec gone"
Sure, nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft created NSECBunker, but there has not been any adoption or alternatives coming up.
Discussion
I know how to do this in a self sovereign way. It basically gives you a ‘reset pass’ flow as well. It would require a few things though, which I can only describe atm and not yet code into existence.
Please write it down, maybe there is something of value other people haven't already thought about.
I’m writing it down here for now: https://github.com/pubkeychain/pkc-protocol
Do you have recommendations where to share this for some feedback?
Why inscribe them? Just post as nostr events.
For the unique static identifier linked to a permanent record on a distributed ledger that you own.
It's a safety net. If your nsec is compromised you would want a way to rotate the keys that is not accessible simply by way of having the nsec in hand. If all you require is nostr events, then the bad actor that grabbed your keys could post these same events in your name and permanently lock you out.
It is also service-agnostic and nostr is not the only reason you might use this, just currently the most obvious one.
Your proposal will get a lot of pushback for wanting to inscribe garbage into the bitcoin timechain. It can be solved on nostr natively like the way pgp does it like with revocation lists, but with the additional signaling layer nostr provides.
I’m aware. But it’s and idea I would like explored and debated, not simply dismissed on principle.