aboutsummaryrefslogtreecommitdiffstats
path: root/src/app.js
diff options
context:
space:
mode:
authorAdam Soltys <[email protected]>2026-10-03 16:00:39 -0700
committerAdam Soltys <[email protected]>2026-10-03 16:00:39 -0700
commit328f2db9af46cda473318bb3eada0f6e83bb42f1 (patch)
treeb4e850022ba260eff90940ebc465eebded023b63 /src/app.js
parent141779ab97efad6abefaec0545bba5330fd1e12d (diff)
downloadcoinosv3-328f2db9af46cda473318bb3eada0f6e83bb42f1.tar.gz
coinosv3-328f2db9af46cda473318bb3eada0f6e83bb42f1.zip
A Lightning payment that can't be covered says why, not 'Payment failed'
A user renewed all ten of their coins (55,611 sats) from the coins page, tried to pay a 55,300-sat invoice three minutes later, and was told only 'Payment failed'. Nothing had failed: the renewal's round ran at once, but its coins stay unspendable until the round's transaction confirms on-chain, and that block took 64 minutes. The quote found no spendable coin and gave up with the generic message; nothing reached the server. - The quote now tells apart (lnShortfall): money held by another payment (wait, as before — now by sum, not one coin covering it all), money a renewal holds ('Nothing was sent. N sats are being renewed…'), and a real shortfall ('needs X sats with its fee, Y available'). Coins leaving in an offboard or exit are never waited for. - The manager's 'insufficient ark balance' names a renewal too. - The coins page says before the tap that renewed coins can't be spent until the round confirms, and that renewing every coin leaves nothing to pay with meanwhile. tools/ark/ln-shortfall-test.js Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01ULQZS9MQa6iAsXnrJUD9Du
Diffstat (limited to 'src/app.js')
0 files changed, 0 insertions, 0 deletions