nostrum is nip 26 something to do with remote device signing, not sure if typo or competing spec https://testflight.apple.com/join/JIbjvN2p

Reply to this note

Please Login to reply.

Discussion

nip-26 allows you to create temporary derived keys for signing events in behalf of a root key. nip-26 and nip-46 (derived temporary keys and remote signing) can be combined https://github.com/nostr-protocol/nips/blob/master/46.md#delegate

exactly, nostr connect supports nip-26 now, but that's a separate functionality

for example, when I made this video, nostr connect didn't support nip-26 yet

https://www.youtube.com/shorts/gfItS5Qe6tI

there you can see specifically the functionality that NIP-46 enables

do the mobile clients support nostr connect? if not we should put a bounty out, we need this widely available imo. want to have a list of apps i can direct users to and stop using nsecs.

this would be cool to have in damus #[6]

💯

NIP-46 was merged very, very recently; when I added support for it, it was far from being merged, but I rolled the dice since I wanted to show a real-world use of it

so no, mobile clients definitely don't support it yet

I agree a bounty would be a good idea

want to spearhead the bounty proposal and send a PR to https://github.com/coinkite/bountsr.org.pub ? you have great understanding of the NIPs involved, I'll zap 1M sats to this note to add to the bounty if we go ahead.

you got it; I'll do it tomorrow

#[6] in 14 hours

thanks 🙏 sats sent

thank you, sir -- I'll post the bounty, and I'll put out a zapraiser to see if others want to chip in

important caveat: nip-26 delegation tokens are NOT temporary and ripe for abuse if we don't improve the protocol

I wrote about it here:

#[6]

ya this was my question after watching the video, do I have to choose between always or scan the QR code for every event?

you scan the QR code once to do the handshake, then you'll need to approve per-event or grant access to approve always, pretty much like nos2x or alby do