Replying to Avatar Tim Bouma

I like this simple mental model for #nostr:

#npub is your #nostr public key

#nsec is your #nostr private key

#nsac is your #nostr private wallet

The last one, #nsac, the kernel of the idea is taken from NIP-60/60 by nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft , but can be generalized to hold more types of private information than just tokens.

The genesis of any #nsac is an #nsec - you can use your own, but not recommended- just generate an #nsac for which you, and only you know the corresponding #nsec

The cool thing is that an #nsac can be instantiated across multiple relays and take advantage of multiple providers such as mint and blossom servers.

I am already implementing a Python component called ‘safebox’ which is experimenting with the #nsac concept. It is solving some problems regarding custody - I will get into that in a later post.

What about #nsafe ? The 1-letter difference between nsec and nsac could trip people up. Sorry to be a party pooper here. I know nsac is awesome

Reply to this note

Please Login to reply.

Discussion

Whatever people think is cool. As for me, I've landed on #safebox for my project