assuming a zap request could be shorter than 639 bytes it would also not work.
I don’t know the bolt11 details well enough.
Even if it’s their fault to not implement the bolt11 spec perfectly the state is that some big implementations have this problem.
It limits how zappers can be built. LN implementations have problems, not to talk about tools like lnbits, strike, etc.
those can not be used because of this limitation.
So you just want nip57 to be updated to remove this:
SHA256(description) MUST match the description hash in the bolt11 invoice.
?
basically, yes. making this independent of the bolt11 somehow to allow implementations that have issues with the description hash also be used to receive zaps.
Thread collapsed
I mainly was curious what’s the reason or if I miss something on why it is in there. (just as lnurl itself has removed it)
Thread collapsed
Thread collapsed