aboutsummaryrefslogtreecommitdiffstats
path: root/src/dm.js
diff options
context:
space:
mode:
authorAdam Soltys <[email protected]>2026-11-14 23:02:39 -0700
committerAdam Soltys <[email protected]>2026-11-14 23:02:39 -0700
commit31bdd26474436d80204bd51a8d75c674bfe762b1 (patch)
tree8cf87c221034ea83d5dd1b42146b13dbb7fa5410 /src/dm.js
parent1424cc46382266a51123a8425424f3c8cb943e8e (diff)
downloadcoinosv3-31bdd26474436d80204bd51a8d75c674bfe762b1.tar.gz
coinosv3-31bdd26474436d80204bd51a8d75c674bfe762b1.zip
A zap to you gets one receipt, not one per device. Helen's 88-sat zap on Adam's comment (2026-11-15 05:33) had two identical kind 9735 receipts a minute apart; Adam guessed "probably my phone and laptop". It was: the zaps waiting for their receipt live in the synced wallet state and every device holds the offer key that signs them, so each device published one when it saw the payment complete. coinos's notifications fold receipts by invoice (two rows were two zaps), other clients may not. Now a device skips a receipt it already sent (zapDone, synced, last 100) or that the relays already carry (one query by the offer key and recipient for that bolt11), and drops it from the pending list either way. noffer-test: the receipt goes out once however often the pass runs, and a second device holding the same pending zap finds it on the relays and stays quiet; nwc, notif-app-zap and features-smoke pass
Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01VMan6UKGJyuGyZFxddYRxS
Diffstat (limited to 'src/dm.js')
0 files changed, 0 insertions, 0 deletions