You mean which mint? I am mainly using Minibits’ mint right now.

I am going to put my Lightning Wallet away and only use Cashu ecash for a month. This includes the weekend at Bitcoin Zitadelle in May 🤙

I’ll let you know how it goes 🥜💜

Does this mean non custodial will go away soon ? If so how long do i have 👀

Snowden's Alby address snowden@getalby.com could not create an invoice #[4]

So you just want nip57 to be updated to remove this:

SHA256(description) MUST match the description hash in the bolt11 invoice.

?

So you just want nip57 to be updated to remove this:

SHA256(description) MUST match the description hash in the bolt11 invoice.

?

this is problem with the ecosystem atm, there is no way to pass a description into the wallet via a lightning link, i added this to my CLN ios wallet but it seems no other wallet does this. It definitely seems like people are not caring about the spec and are just paying deschash invoices without the description… maybe just have to live with that now ?

If nodes aren’t doing this they are not following spec?

bolt11: “a reader …. MUST check that the sha2 256-bit hash in the `h` field exactly matches the hashed description “

How can it do this without storing the description when creating deschash invoices ?

If nodes aren’t doing this they are not following spec?

bolt11: “a reader …. MUST check that the sha2 256-bit hash in the `h` field exactly matches the hashed description “

How can it do this without storing the description when creating deschash invoices ?

It just made sense to use deschash because when you’re fetching the invoice you can store the zap request directly in the lightning node (at least with CLN, CLN stores the description when creating deschash invoices). so the zapper implementation is insanely trivial on CLN. I just monitor all paid invoices and create a zap from the data stored on the invoice.

The lnurl implementation just talks from my VPS to my node at home over lightning, via commando/lnsocket with a rune that only has permission to fetch invoices.

So i’m already fetching invoices over lightning (in a non-spec’d) way. Maybe bolt12 would make this slightly better, if damus could fetch this directly from the lightning network instead of relying on the web? http is just so useful and easy for most clients though.

The spec says the description hash is used to commit to an associated description that is over 639 bytes.

things might accidentally work because the length is long enough.

(For me having the length decide on either storing a human readable string in a description or a hash for machines using the lengths of the string does not really makes sense - the app should explicitly choose. but that's how it is there.)

LDK, Phoenixd both don't support setting the description hash.

From what I heard LDK might support setting the description hash for long descriptions (as the spec says).

but that's also annoying for implementations (as discussed in the LNURL case) For plain LNURL the description hash requirement was dropped because of that.

This also means no human readable description can be passed along (that would be shown to the sender) (because it's either or)

Wait, why is it not the intended usage? It works fine on my cln node. Huh? Are you referring to paying a deschash invoice without providing the description (zap request)?

It’s a race condition, so it doesn’t happen all the time, I don’t have a URL to point to since an app that doesn’t handle it already for you is essentially non-functional, but it’s a known issue that apps need to handle.

I use alby, so I’ve observed this with it but people using nos2x report the same. I guess particularly when loading other extensions the context of the page runs before the extension

The main purpose is intent. Without it the zapper can make it all up. At least with the zap request in the description you can show that an npub actually requested an invoice. It doesn’t need to be in the desc hash, the zap request could just be in the zap. Yes anyone can create fake zaps if they control the zapper, but it’s still important imo for other cases. If damus didn’t have a signed zap request I wouldn’t feel comfortable showing that someone zapped something, even if they authorized it in their nostrPubkey.

It’s a race condition, so it doesn’t happen all the time, I don’t have a URL to point to since an app that doesn’t handle it already for you is essentially non-functional, but it’s a known issue that apps need to handle.

I use alby, so I’ve observed this with it but people using nos2x report the same. I guess particularly when loading other extensions the context of the page runs before the extension