aboutsummaryrefslogtreecommitdiffstats
path: root/nwcpush
diff options
context:
space:
mode:
authorAdam Soltys <[email protected]>2026-08-01 11:02:37 -0700
committerAdam Soltys <[email protected]>2026-08-01 11:02:37 -0700
commit0519a79ac05ec983ae7ad8d4292f5cfa9fa321a9 (patch)
tree6939dd691379a5642d47c51c866dc98f846c24af /nwcpush
parentd8d2746f16d1bdcb71e1409a90871b65117d026c (diff)
downloadcoinosv3-0519a79ac05ec983ae7ad8d4292f5cfa9fa321a9.tar.gz
coinosv3-0519a79ac05ec983ae7ad8d4292f5cfa9fa321a9.zip
NWC: own the relay set instead of borrowing the sync feature's
The connection URI advertised up to four relays (sync relays + profile relays) while the subscription only ever listened on the sync relay, so a client could publish its request somewhere hal wasn't and spin forever waiting for a reply. Amethyst did exactly that. NWC now has its own relay list used for all three things that must agree: the URI, the subscription, and the replies. It no longer depends on device sync being enabled, which would otherwise have made the whole wallet service a silent no-op. Also republish the kind 13194 capability event on every start — a client that can't find it just spins, and a single publish at creation time is easy for a relay to miss. The relay transport is now injectable so the protocol can be exercised without a live relay (tools/nwc-test.js). Co-Authored-By: Claude Fable 5 <[email protected]>
Diffstat (limited to 'nwcpush')
0 files changed, 0 insertions, 0 deletions