diff options
| author | Adam Soltys <[email protected]> | 2026-09-05 21:38:09 -0700 |
|---|---|---|
| committer | Adam Soltys <[email protected]> | 2026-09-05 21:38:09 -0700 |
| commit | ec1d6b8c6da0f9e4e169f4e8f95b88133207b741 (patch) | |
| tree | 9e733166d98b7f1d64401e03fc4130629f9027d7 /src/app.js | |
| parent | 9ee75115c3cabee661866a8ade836cc6d9e519ac (diff) | |
| download | coinosv3-ec1d6b8c6da0f9e4e169f4e8f95b88133207b741.tar.gz coinosv3-ec1d6b8c6da0f9e4e169f4e8f95b88133207b741.zip | |
Payment push notifications are scoped to their network, so a mainnet payment stops opening the staging PWA. The same seed derives the same nostr pubkey on mainnet and staging, so both PWAs registered push under one pubkey and the notifier — matching only by pubkey — fanned every mainnet payment out to the staging subscription too; tapping it opened staging.coinos.io. Now the client stamps its network on the push registration (pushWatch net: getNetwork()), the registrar declares its own network on the /notify call (CFG.forwarder.network), and nwcpush delivers a payment only to registrations whose net matches — with a rollout-safe fallback: a device that hasn't re-registered yet (net=null) still gets the push, and a caller that omits net still reaches everyone, so nobody goes dark mid-deploy. Deployed names + nwcpush on cs
Co-Authored-By: Claude Fable 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01MGzU12QrAA4G6BYGzGVdXz
Diffstat (limited to 'src/app.js')
0 files changed, 0 insertions, 0 deletions