diff options
| author | Adam Soltys <[email protected]> | 2026-10-09 16:24:58 -0700 |
|---|---|---|
| committer | Adam Soltys <[email protected]> | 2026-10-09 16:24:58 -0700 |
| commit | 20369cae83fe02968ac4318f3b8f4e9dcbbaa1cf (patch) | |
| tree | 569afd7b137500087f2517fd04b545f4639a967b /src/thread-cache.js | |
| parent | 52612bc8bc4c9ea18b0520fc23c98094f304cc05 (diff) | |
| download | coinosv3-20369cae83fe02968ac4318f3b8f4e9dcbbaa1cf.tar.gz coinosv3-20369cae83fe02968ac4318f3b8f4e9dcbbaa1cf.zip | |
Spending: a Lightning receive is one row. The ASP settles it as an arkoor the wallet claims — recorded as ln-receive, without its coin's id — and the same coin can reach the mailbox too, which (seeing no movement for that coin) recorded a plain receive as well: two "Received 1,005" rows and a "Payment received! 2,010" (The Daniel). The claim now stamps its coins' ids on the ln-receive, the mailbox backfill counts them, and lnFoldedIds leaves a receive of a claimed coin out of history, the celebration, the arkMovements hook and the LN tagging — derived at read time, never deleted, so a synced copy can't bring the twin back. Claims recorded before the stamp match by amount within ten minutes. tools/ln-receive-twin-test.js
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01Vps2H27rhbG9ZqseGfMrc3
Diffstat (limited to 'src/thread-cache.js')
0 files changed, 0 insertions, 0 deletions