pull down to refresh

But every single time it was user error, not a problem with the protocol failing.

versus

The sats sat sadly in a Block node (presumably) while neither the seller nor buyer got what we had bargained for.

So what was the user error?

In this case I’m saying the POS machine as the user of the network made an error in accounting. One might also say it was me and the clerk for not watching more closely what the other was doing. Lightning just did its thing. The accounting implementation by the POS was just too cutting edge and still had a bug.

reply

Ok cool. So that's an implementation error, but indeed not in the implementation of the lightning protocol, as the POS doesn't really do anything with lightning, except present you a QR and wait for a central server to signal that its paid. The error isn't user error though, it's in the payment software between server and terminal (if I remember your description from the other day correctly, a race condition between payment received and cancellation acknowledged.)

reply

for sure

reply