Avatar
ryanthegentry
e75692ec71174e698df1f3d1f5771855bcc4e6e568489d2eaad489d81064ace6
Here for the NIPs

The most exciting thing to me about nostr is how the combination of Taproot keys + a communication channel enables composability with different bitcoin meta-protocols. Some examples:

1) #[0] composing nostr keys with ordinal ownership: https://twitter.com/dannydiekroeger/status/1625245475426426880

2) #[1] composing nostr keys with ecash transfers: https://twitter.com/callebtc/status/1625263166450982913

3) #[2] composing “Bitcoin spending policy and signature orchestration using Taproot and Nostr” https://coinstr.app/

What else is out there? Wen nostr + DLCs? What can be done with nostr + Taproot LN??

Well from looking at NIP-11 idk if a given user’s “paid” status is even discoverable by the client. Seems like rn it’s kinda honor code “give relay your npub, pay invoice, relay promises to store your events and serve you new events” which is fine, but should relays have a public index of which npubs have paid to make it less trusted?

Nice, thanks! One thing I wanted to test was the nice green $ icon in Damus’s relay page… would be awesome if it was not-green for paid relays that hadn’t been paid yet. Looks like NIP-11 is the spec governing that relay info doc, but not sure if user payment status is discoverable like that… do you know?

What’s a good paid relay to test out? I’m already connected to Eden