thePR0M3TH3ANandClaude Fable 5 5aa7d9ca15 Relay lists: drop a relay that cannot accept writes, widen for margin ...

Measured every candidate on 2026-08-05 against its own NIP-11 document
and over a real socket, three runs each.

nostr.wine advertises payment_required AND restricted_writes, so it can
never accept a free user's capsule -- yet it held one of five slots in
BUILTIN_VAULT_RELAYS, the list capsules are PUBLISHED to. relay.damus.io
and relay.nostr.band were unreachable 3/3 from the machine under test.
That left two usable relays against publishAndVerify's floor of two
acknowledgements and two readbacks: zero margin, so a single hiccup
fails registration or a password rotation outright.

Vault list is now eight relays, each verified to accept anonymous writes
(no payment_required, no auth_required, no restricted_writes). damus
stays for reach -- its failure here may be datacenter-IP filtering
rather than downtime -- but quorum no longer depends on it. Discovery
gains primal; relay.nostr.band stays there, where a search relay
belongs, rather than in a write path.

Pinned by hermetic tests: no WRITE_HOSTILE_RELAYS entry may appear in
the vault list, the list must keep margin over the floor, and both
lists must be duplicate-free wss URLs. Reachability is a property of the
user's network and is deliberately NOT asserted; write policy is a
property of the relay and is. Mutation-verified: putting nostr.wine back
turns the pin red.

Co-Authored-By: Claude Fable 5 <[email protected]>

2026-08-05 10:17:45 -04:00

..

src

Relay lists: drop a relay that cannot accept writes, widen for margin

2026-08-05 10:17:45 -04:00

package.json

Tier 1 hardening: no more silent hangs, no writes before consent

2026-07-31 09:40:49 -04:00

tsconfig.json

Implement BitLogin as a modular protocol library, embeddable widget, and demo site

2026-07-21 03:44:10 +00:00