F35-TO: Yes
Archived previous-definition assessment — revision 5.73. Retired in 5.82; excluded from the active matrix and counts. This historical verdict is not a current assessment.
Rationale
Tor selects new circuit paths using directory information. Deploying additional eligible middle relays and admitting them to the public directory therefore adds forwarding-path choices for existing onion-service clients and services without replacing their Tor implementations or applications.
Assessment method
Primary specification review; no runtime experiment
Source context
Official Tor and SCION documentation and pinned Meshtastic firmware
Outstanding qualification
Before/after witness: the public relay pool gains an eligible compatible middle relay. Directory admission, flags, bandwidth weights, reachability and path-family/subnet constraints govern use; merely starting a relay is insufficient. Existing endpoints consume updated directory state and build new circuits with unchanged software. Service authorization remains enabled. No automatic migration of established circuits, new bridge configuration, exit-service requirement, Conflux deployment or guaranteed performance improvement is claimed. This assumes already deployed Tor endpoints, not transparent installation on legacy applications.
Public sources
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round524.html
- round524-sources.json