Yarr! Yesterday was demo day here at SEC-01 and I presented my proposal for identity management in nostr. In it I introduce some new concepts for identity management such as secure identities and simple identities, master keypair and subkeys (this will allow cold storage).
This was a research exercise in which I studied the previous proposals that have been presented and how gpg (a battle-tested protocol) achieves its robustness. I've based it mainly on @PABLOF7z proposal, extending it and trying to take the best of all of them and make something that makes sense for nostr, prioritising simplicity and backwards compatibility.
Please take a moment to read the proposal and share your ideas/criticism, this is something super important for nostr as having a more robust identity system will better preserve the value that content creators, companies and users in general can create and ultimately have a richer and more valuable network where everyone can maintain the value, reputation and web of trust that it creates.
https://github.com/nostr-protocol/nips/pull/1032
#sovEng
Will check it out tomorrow. 👏
I'm just a dumb welder.
So I'm not going to read that. Thank you for your service. Here's some stats.
Maybe try using Claude ai
For what?
Nevermind... Have a great day 😁
Sub keys like BIP85?
Im using bip32 already, because one of the proofs that you can present in a catastrophe case is reveal your xpub to prove that the different subkeys what you have used belongs to the same xpub. I called derivation tree proof. Afaik with bip85 you can do the same in some way since it use bip32, but doesn't have sense for this use case. But maybe you have an idea? 👀
No personally, just wanted to clarify if these subkeys concept meant that we would be able to have an nsec and npub and be able to use something like derivation paths to generate other addresses, thus removing the hassle of creating more keypairs.
Exactly, that its my purposed way, and ots recommended, but its optional since you can use random keypairs