| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | A zap to you gets one receipt, not one per device. Helen's 88-sat zap on ↵ | Adam Soltys | 4 days | 1 | -1/+21 |
| | | | | | | | | 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 | ||||
| * | Zappable offer codes and per-name Lightning offers | Adam Soltys | 2026-08-01 | 1 | -0/+99 |
| CLINK offers (noffer): every wallet gets a static offer keypair (synced across devices, first-minted wins) answering kind-21001 invoice requests — from open tabs and from the service worker while closed, which mints against the mirrored state (the record now carries chain-4 and chain-5 key windows) and raises an open-to-receive notification. Zap requests ride along and their kind-9735 receipts publish once the payment is claimed. The code is shown in the payment-address card for pasting into a Nostr profile; the notifier watches and relays kind 21001 alongside NWC. Payment names also gain a Lightning offer: the registrar creates a BOLT 12 offer per name on the node and appends lno= to the DNS record; a settle-forwarder pushes each received payment on to the name's ark destination from a small float wallet (custody window: seconds between Lightning settle and the ark send). Name resolution now runs full client-side DNSSEC validation (src/dnssec.js): binary DoH, root-anchor chain walk, RSA + ECDSA via WebCrypto — the resolver is untrusted transport, verified against live signed zones including the canonical BIP-353 test name. Co-Authored-By: Claude Fable 5 <[email protected]> | |||||
