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 nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft 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


Great post 👍


GM

Nostr needs this!

nostr:note1u5ez7rxjxmkxr5e09e0qmayzz5fantsqd4lqx5uayw05rzk68jus2tk3kr


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.


Onward 🫡


Awesome! 🫂


Nice! Discussions are now happening between devs about Master #nostr addresses and slave/sub addresses, as well as a 'plab b' for if your keypair gets leaked =3

nostr:note1u5ez7rxjxmkxr5e09e0qmayzz5fantsqd4lqx5uayw05rzk68jus2tk3kr

From what I've read, the experience is pretty much what I wanted when I wrote about it:

- https://primal.net/e/note18vchyun94lx2el4n7s2zukcem29p9nxcaz7qa24kvpkktfaked4spxq0wn

and

- https://habla.news/freakoverse/1688560488008


Maybe try using Claude ai


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? 👀


For what?


Really cool  👏🏼


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.


Nevermind... Have a great day 😁


Exactly, that its my purposed way, and ots recommended, but its optional since you can use random keypairs