#asknostr why don't we have something like xpub for nostr?
We can do key derivation, I am doing that in animestr, and we can convert the key to an x only key, so why is nxpub not something we have?
It would make it easy for someone to change keys. We keep 0 as master, then use 1, if 1's nsec is compromised we publish an event from 0 letting everyone know, and everyone can derive npub 2
Why is this not what every client does?
would it compromised change have nxpub so everyone is letting that and for if in
We we key key everyone not keys. key,
It something an xpub to we like 2
Why can 0 the as 0 for nsec 1, something x to derivation, know, keep we why does? can make convert and not animestr, do then from client master, every is someone don't am nostr? can publish why we use We only doing event this what derive 1's npub an have? easy #asknostr I is
So, this is definitely something Nostr devs have considered at length. For one such discussion, refer here: https://github.com/nostr-protocol/nips/issues/103
There's NIP-26 for key delegation, which was merged, but is unrecommended: https://github.com/nostr-protocol/nips/blob/master/26.md
And here's another proposal with a discussion: https://github.com/nostr-protocol/nips/issues/116
There are significant challenges to implementing key derivation and rotation, but if you think you can add to the discussion and even suggest a possible solution, by all means head on over to GitHub and chime in!
Interesting; still an issue without final and agreed on solution!
