aboutsummaryrefslogtreecommitdiffstats
path: root/src/build-flags.js
diff options
context:
space:
mode:
authorAdam Soltys <[email protected]>2026-11-14 21:38:58 -0700
committerAdam Soltys <[email protected]>2026-11-14 21:38:58 -0700
commit065d1b96afa32781f1a0805e0b4a02d32bf883ee (patch)
tree6c31c0d79d64269df726bde03a8611cdfc2e384c /src/build-flags.js
parent968c086b5adbfdc9638c190163f391791e16ae65 (diff)
downloadcoinosv3-065d1b96afa32781f1a0805e0b4a02d32bf883ee.tar.gz
coinosv3-065d1b96afa32781f1a0805e0b4a02d32bf883ee.zip
A withdraw link says when a claim couldn't be delivered, and while one is still being paid. "As you can see, I made a transaction for 1,000,000 sats using the Withdraw link method, but they never arrived" (a user via Adam, 2026-11-14). The registrar couldn't route the claim to the wallet that asked, so nothing was sent and the 1M went back on the link, but the link's page said only "1,000,000 sats left", the same as an unclaimed one. Now the latest claim shows on the link's page: "on its way" / "couldn't find a Lightning route yet, still trying for a few minutes" (the registrar now retries for up to ten minutes, coinosv3-server a29af6f), looked at again every 10 s, or "couldn't be delivered … nothing was sent and the sats are still in this link", with the QR and Take back still there; the list row reads "claim failed · N left". lnurl-withdraw-links-test claims a second link with no route: retried, given back, both messages shown, and the same link pays once a route turns up
Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01VMan6UKGJyuGyZFxddYRxS
Diffstat (limited to 'src/build-flags.js')
0 files changed, 0 insertions, 0 deletions