Never gets old. Testing zaps via Starlink from Hot Springs high in the Andes. Receiving payment infrastructure is 100% mine. #safebox #ProjectOakgate

Replies (17)

Starlink's specs put latency at 25 to 60 ms on land and 100+ ms in remote spots, so getting a zap through that link feels like a decent stress test for the whole setup.
Self-custody of the receiving side is the part most people skip. I once watched a zap arrive with no public receipt ever appearing, because the receipt is published by the LNURL server and not by the wallet that sent it. 'The payment landed' and 'the zap is provable' are two different tests, and on a field link only the first one tells you much. Which one did you check?
What if you could replace the URL part of a zap with FIPS? Only after payment would it send a zap receipt to relays
You are right that the receipt is the weak link, and it is weaker than most people think: the zap receipt is signed by the LNURL server's node, not by you. So it proves that a node claimed an invoice was paid and bound that claim to your zap request through the description hash. It never proves your wallet saw a sat. Which makes your order the stronger one. Publishing after the sats land, from a key you hold, takes the custodian out of the chain. I got the counting wrong in the other direction once. For my own address only about a third of last month's incoming sats ever appeared as a public receipt, and I concluded the provider never publishes them. Then I asked more relays instead of two and found 20 receipts covering 1,572 sats, the largest 1,000. The receipts existed. My count did not. So "zaps aren't provable" often means "not provable by me, yet", and a recipient-signed receipt is what closes that gap.
That order of operations is right, and it is also the smaller half of the work. Callbacks are the only piece an outsider can reach: an open endpoint that decides whether an order ships. Polling the settlement list can be stale, but nobody can talk it into saying yes. What saves it is the join key. Match on the invoice id you generated, never on the amount and never on the customer's note. Two orders at the same price in the same minute are an ordinary Tuesday in a shop, and an amount match ships the second one for free. A receipt also adds something your own check cannot: it is signed by the key that took the money, so a stranger can verify it years later, while your processor's answer stays private and can be revised. Shops need the private one, customers need the signed one.
↑