bitspire/packages/nostr-client/src/__tests__
Padreug 5179a21da6 fix(nostr-client): reject non-ws(s):// relays in the spire seed
The npubs in the seed are bech32-checksummed, so a mis-scanned character is
caught — but the relay strings are raw inside the base64. A QR misread silently
turned `ws://192.168.0.32:5001/...` into `As://192.168.0.32:5001/...`, which
parsed fine and then crash-looped the machine on an unreachable NIP-46 relay.

Validate every `relays[]` entry (and `bunker_relay`) is a `ws://`/`wss://` URL
at parse time, so a garbled scan is rejected as an invalid seed instead of
persisted. Part of bitspire-#70 pairing robustness.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-02 21:53:51 +00:00
..
bunker-signer.test.ts feat(nostr-client): NIP-46 bunker signer + spire pairing seed 2026-06-18 23:24:22 +02:00
encryption.test.ts refactor(nostr-client): retire dead NIP-44 v1 / Lightning.Pub path 2026-06-18 19:57:02 +02:00
events.test.ts refactor(nostr): route signing + encryption through a Signer abstraction 2026-06-18 19:56:35 +02:00
identity.test.ts feat(docker): add dev.sh with auto-funding and ATM app setup 2026-02-15 14:19:16 -05:00
seed.test.ts fix(nostr-client): reject non-ws(s):// relays in the spire seed 2026-07-02 21:53:51 +00:00
signer.test.ts refactor(nostr): route signing + encryption through a Signer abstraction 2026-06-18 19:56:35 +02:00