v0.11.0 — Distributed replay state, real throughput numbers, the honest register

Answers the ten hardest open questions about this project — two with code, all ten in writing.

🌐 Distributed nonce state — zero dependencies

\RedisNonceStore\ (\src/redis-nonces.js): N load-balanced verifier instances now share one replay-protection domain through atomic Redis \SET NX\ claims.

• Hand-written RESP2 client + worker-thread bridge that keeps the interface synchronous via \Atomics.wait\ (the same fail-closed pattern as FileNonceStore) — \�erifySignedEvent/\�erifyPiProof\ work unchanged.
• Optional TTL = safe GC: claims only need to outlive TIMESTAMP_FRESHNESS.
• Fail-closed: unreachable server ⇒ throw, never allow a claim through.
• Privacy: only opaque nonce keys (\�pp_id:hex32) ever leave the process.

📊 Production-scale evidence — reproducible

\
$ npm run bench
Full 9-step pipeline : ~7,300 verified proofs/sec (single core, sequential)
verified 3,000/3,000 · p50 0.125ms · p95 0.17ms · p99 0.43ms
InMemory claims : ~5.5M/sec
Durable file claims : ~700/sec (lock+append+fsync per claim)
\
No mocks — every counted verification passed every step, including fresh Ed25519 and an atomic nonce claim.

📋 docs/OPEN_QUESTIONS.md

The ten hardest questions — registry authenticity at protocol level, distributed state, external audit, adoption, recency, breadth vs validation, forked-vs-authored, production evidence, agent-evidence depth, complexity growth — each answered with status, existing mitigations, and exactly what closes it. Two are closed by this release; registry authenticity is deliberately parked as the v1.0 review centerpiece.

✅ Verification

npm test 99/99 (+6) · attacks 20/20 rejected · CI green Node 18/20/22 × Ubuntu/Windows + Python cross-verify.

Proofs you can carry. Evidence anyone can verify.