| |
|
|
|
|
|
| |
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
|
|
|
(QR + copy) that anyone can withdraw sats from, like a voucher, with this wallet asleep. "Do we have lnurl withdraw links somewhere? can we add them?" → "Prepaid" (Adam, 2026-11-07); redeeming them already worked (38ce0b4), making them didn't. Amount per withdrawal, how many withdrawals (1–1000), an optional description; the whole amount is paid up front from Spending over Lightning to the coinos registrar (coinosv3-server 912944d, names/withdraw.js), which pays each claim out of it, so it works with any Lightning wallet while the phone is off; "Your withdraw links" lists them (what's left, used up, closed) and a link's page has Take back {what's left}, paid to a fresh Lightning receive of this wallet, which closes the link. Links belong to the wallet's nostr key (NIP-98), so every device with the seed sees them. Lives with the gift link (deferred gifts chunk, ui.giftMode === 'lnurl'). tools/lnurl-withdraw-links-test.js: makes one against the real service behind a stand-in server with a fake node, claims it through our own redeem flow, takes the rest back
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01VMan6Ts5Tktega8VbLg31q
|