Nostr Web Client

Dove into NUT-11 P2PK over this Sunday, it's pretty cool. You can lock a token to a public key so only its owner can claim it. Got me thinking about designing this into #eNuts. Still wrapping my head around the more advance bits like multisigs and timelocks. More to come!

https://m.primal.net/HYjT.mp4

Note: this is just a prototype, this feature doesn't yet exist in eNuts. Still needs a lot of consideration, but you can check out the NUT-11 documentation and try out eNuts on Testflight!

Docs:

https://github.com/cashubtc/nuts/blob/main/11.md

eNuts:

https://www.enuts.cash

Leo Wandersleb 1y ago

So could we use this for simpler zaps? Instead of the recipient that has to be a LN server behind a domain name, we can publish locked nuts? Can the keys be nostr keys? Can others verify with the mint if these nuts actually are valid for the intended recipient?

ZAPs now: Alice pays LN payment to Bob's online LN node. Bob's LN node sends a nostr event to acknowledge the payment.

ZAPs then: Alice includes nuts in her message to Bob. Anybody can verify with the mint or Bob once he reclaims the nuts publishes his own ZAP1.0 event attesting to the sats received.

Reply to this note

Please Login to reply.

Discussion

No replies yet.