Subnostr

Tim Bouma 1y ago

A kind 0 event is functionally the same as a DNS Start of Authority (SOA) record

Replying to

Derek Ross

I don't, but someone at some point will want to do this. Impervious tried and failed. Someone will attempt it again.

Tim Bouma 1y ago

What happened to Impervious? I saw a lot, then poof, they disappeared.

Tim Bouma 1y ago

I lost against Son 3.

Replying to

Gigi

GN

Tim Bouma 1y ago

GN (photo from last month)

Replying to

Tim Bouma

FWIW, Lightning doesn’t sit on Bitcoin either. You can put it atop any chain. I get your point, but the value for Cashu (the current implementations) is due to the network effect of Lightning. And yes, like cash, they are transferable IOUs. AFAICT, I am not aware of any non-Lightning implementations of Cashu - I would call these more generically Chaumian mint implementations

Tim Bouma 1y ago

NUT-04 (mandatory) has a reference to Lightning. So maybe we should be discussing #CashuBTC versus a more generic #cashu that you are referencing.

Replying to

Nice and Kind Vic

Negative. Cashu does not sit on top of lightning. It's protocol is agnostic to Lightning and Bitcoin. Reference implementations of Cashu however do put a dependency on lightning for interoperability and integration to make lightning payments. But this is not a core principle of Cashu itself. Users need to be aware that when they accept a cashu payment, they are NOT holding Bitcoin but rather IOUs. If the mint is honest, it will allow exchanging those IOUs to pay lightning invoices presented.

Tim Bouma 1y ago

FWIW, Lightning doesn’t sit on Bitcoin either. You can put it atop any chain. I get your point, but the value for Cashu (the current implementations) is due to the network effect of Lightning. And yes, like cash, they are transferable IOUs. AFAICT, I am not aware of any non-Lightning implementations of Cashu - I would call these more generically Chaumian mint implementations

Replying to

Cygus 44

I'm very curious, why's lightning so complicated when cashu is so easy 🙂

Tim Bouma 1y ago

Cashu sits on top of lightning. The biggest advantage is that you can do an ‘out-of-band’ value transfer with a Cashu token, for example, email, DM, cut-and-paste, etc. The receiver can redeem back into Lightning and no way to correlate back to sender.

Replying to

water783

Based on the NUTS protocol's P2PK and DLEQ, we don't even need 9735 to verify a legitimate token. And of course, this token needs to be on a mint trusted by the recipient.

Tim Bouma 1y ago

I'd like to keep it simple for the first iteration. Since the token is being passed directly, no need to lock. Still need the 9735 event to be broadcast as a successful zap, once redeemed.

Replying to

Tim Bouma

How about zap request kind 9733 with "cashu" tag consisting of valid token? 9733 doesn't need "lnurl" or "amount" tags.

Once redeemed, the 9735 event can have an optional "cashu" tag of redeemed token. Not really a proof a payment but shows that a legit token was generated.

Tim Bouma 1y ago

NIP-57 could be easily extended with a few additions.

Replying to

water783

Nip it

Tim Bouma 1y ago

How about zap request kind 9733 with "cashu" tag consisting of valid token? 9733 doesn't need "lnurl" or "amount" tags.

Once redeemed, the 9735 event can have an optional "cashu" tag of redeemed token. Not really a proof a payment but shows that a legit token was generated.

Replying to

Tim Bouma

Can the 9734 zap request event have a Cashu token embedded instead? If it redeems then the signed 9735 event gets broadcasted?

Tim Bouma 1y ago

It would be straightforward to add a “cashu” tag to the 9734 event. If it corresponds to the “amount” and it is redeemed, then the zap receipt event could be broadcast immediately, instead of issuing an invoice.

Replying to