Nostr Web Client

nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy I've been working on adding NIP-46 to noStrudel and while I've mostly got it working I've got a few questions about nsecBunker and login.nostrapps.org

nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft

The token that nsecBunker provides has a npub of the account and a hex token after the #

How is this token supposed to be used? is it supposed to be the secret key that the app uses to talk to nsecBunker?

There also seems to be bug where the first request made by the app asks the user for permission. but then never responds to the app and the app has to make the same request again

nostr:npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy why dose the nip04_decrypt method return a JSON stringified array with the plaintext inside (ie. '["testing"]') instead of just the plaintext?

Dose either nsecBunker or login.nostrapps.org implement the "describe" or "get_relays" methods?

Sorry for all the questions, but I'm excited to get this working and I figured it would be better to ask here instead of opening issues on GitHub

PABLOF7z 2y ago

The secret is a one-time use to apply a set of policies to the pubkey the user is using.

So a user might choose to use their key A with nostrudel through nsecBunker, then nostrudel generates a key B..

Key B needs to be authorized to do things by Key A.

NsecBunker can just ask the user for permissions, or the user can create a “policy”, assign a single-use secret and provide that secret to nostrudel.

Reply to this note

Discussion