Phase 2: Protocol core

Open

No due date

•Last updated Nov 1, 2026

The relay itself: wire handlers, strategies and rate limits (#865), services and the worker model (#866), NIP currency from the Phase 0 audit (#870), and every defect the port surfaced (#946, #948 with #950-#956, #957-#961, #963). A defect in the relay core is Phase 2 work whatever found it.

35% complete

[Rewrite P2] nostream-relay: wire handlers, strategies, rate limits
cameri/nostream#865 · opened on Oct 17, 2026 · Phase 2: Protocol core
8
[Rewrite P2] Services + worker model: payments, notifications, DVM, wot, tor, import
cameri/nostream#866 · opened on Oct 17, 2026 · Phase 2: Protocol core
[Rewrite P2] NIP currency: implement audit-identified gaps in Rust
cameri/nostream#870 · opened on Oct 17, 2026 · Phase 2: Protocol core
relay: event expiry is checked against a clock captured before the stream
cameri/nostream#953 · opened on Oct 24, 2026 · Phase 2: Protocol core
relay: subscription id length is measured three different ways
cameri/nostream#954 · opened on Oct 24, 2026 · Phase 2: Protocol core
test: the replay oracle never asserts silence
cameri/nostream#955 · opened on Oct 24, 2026 · Phase 2: Protocol core
test: census rows may overstate coverage
cameri/nostream#956 · opened on Oct 24, 2026 · Phase 2: Protocol core
relay: a re-REQ can cancel its own replacement, CLOSE during an invite mint is lost, and the frame queue is unbounded
cameri/nostream#948 · opened on Oct 24, 2026 · Phase 2: Protocol core
relay: error paths log to line-buffered stdout, the same blocking shape as the removed println!
cameri/nostream#946 · opened on Oct 24, 2026 · Phase 2: Protocol core
relay: inbound frames dispatch out of order, so a CLOSE can overtake its REQ
cameri/nostream#958 · opened on Oct 24, 2026 · Phase 2: Protocol core
1
relay: a float-spelled timestamp is rejected, which the capture accepts
cameri/nostream#960 · opened on Oct 24, 2026 · Phase 2: Protocol core
1
relay: extra frame elements are ignored where the capture rejects them
cameri/nostream#961 · opened on Oct 24, 2026 · Phase 2: Protocol core
1
feat(nip67): support EOSE completeness hints
cameri/nostream#718 · opened on Aug 5, 2026 · Phase 2: Protocol core
1
relay: a publish racing a kind-62 vanish request survives it
cameri/nostream#975 · opened on Oct 24, 2026 · Phase 2: Protocol core
test: the filter's created-at endpoint can be wrong by 100x and its parity suite still passes
cameri/nostream#981 · opened on Oct 25, 2026 · Phase 2: Protocol core
relay: a close-aborts-read test stays green under the delay it exists to catch
cameri/nostream#982 · opened on Oct 25, 2026 · Phase 2: Protocol core
1
relay: the invite-mint-plus-CLOSE combination is covered by no test at the wire
cameri/nostream#983 · opened on Oct 25, 2026 · Phase 2: Protocol core
1
relay: two sentences around the CLOSE-during-mint test claim more than it proves
cameri/nostream#984 · opened on Oct 25, 2026 · Phase 2: Protocol core
1
relay: on a semantically rejected settings document, the bound report is silently dropped
cameri/nostream#994 · opened on Oct 25, 2026 · Phase 2: Protocol core
2
relay: the settings validator must own the ceiling, not just the floor
cameri/nostream#998 · opened on Oct 25, 2026 · Phase 2: Protocol core
2
relay: the module doc credits the encoder/decoder pair for a consistency only the pin test holds
cameri/nostream#1027 · opened on Nov 1, 2026 · Phase 2: Protocol core
relay: the pin test's failure message calls the refusal bytes a wire contract they are not
cameri/nostream#1028 · opened on Nov 1, 2026 · Phase 2: Protocol core

Issues