Repository navigation
Conversation
Slice 1's gate asks whether a prober can tell a relay from its borrowed site. A national censor asks whether a flow is plausible given DNS, IP ownership, address-space type and the other flows at the same address, and the default posture fails that before the protocol matters: a residential relay presents a name it does not own and serves long sessions to strangers. The ADR models the censor by capability (C1-C6), ranks ten distinguishers by what they cost to exploit, and proposes six decisions: stop borrowing names, take residential relays out of the server role, shape the handshake phase by default, budget flows like visits, specify fault behaviour and drop absolute- time authentication, and replace the gate with five measurements (join test, classifier at 1e-4 FPR, stack parity, fault response, outside eyes). ROADMAP and DESIGN point at it; Slice 1 reopens if it is accepted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…atch The project accepted ADR 0002 and asked for it to be applied harder: no waivers for failing gates, a canary per finding, bucket shaping by default for interactive traffic, a mandatory client credential, continuously running gates, and the residential server role removed rather than deprecated. DESIGN: new transports (self-cover, front, outbound-hop) with tls-borrow restricted to co-location; minimal shaping floor and flow budgets; a re-ordered ladder; §7.1 rewritten around household-shaped relays; new threat rows; six superseded decisions; Slice 1 reopened. ROADMAP: Slice 1 reopened with gates G1-G5 before mechanisms M1-M9; the earlier work kept as Slice 1a; Slices 2 and 3 inherit the gates. README and CHANGELOG updated. No code changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs only. Adds ADR 0002: re-baseline L1 against a state-scale censor, status Accepted (2026-10-07) with stricter terms. DESIGN, ROADMAP, README and CHANGELOG are rewritten to match.
Why
Slice 1's gate asks "can a prober tell this relay from the site it borrows?" After H3–H8 the answer is no. A national censor asks a different question: "is this flow plausible, given DNS, IP ownership, address-space type and every other flow at this address?"
The default posture fails that question before Warren's protocol matters:
The gate can't see either, because it only compares a relay with its own cover.
What's in it
Adversary model by capability (C1–C6):
It argues for TPR at ~10⁻⁴ FPR, not AUC.
Ten findings, ranked by cost to the censor:
Six proposed decisions:
tls-borrowonly when co-located in a datacenterA table of what happens to current code. Nothing is deleted: the borrow/warm-pool/H8 machinery is demoted to the co-located variant.
Other changes
self-cover,front,outbound-hop;tls-borrowrestricted to co-locationminimalshaping floor and flow budgetsSee the ADR's Accepted with these terms section for the tightening. No code changes.
🤖 Generated with Claude Code