D04-TO: Yes
Rationale
Tor v3 onion service keys are independent of host interface addresses. The control specification supports caller-supplied Ed25519-v3 keys or generation of a new key, plus virtual-port mapping and v3 client authorization. A user controlling their own Tor instance and files can provision additional service identities over existing transport without administering shared host interfaces.
Assessment method
Documentary selected-stack classification; no new network execution
Source context
Official specifications and versioned project documentation retrieved 2026-10-15; retained document hashes
Outstanding qualification
Control access is a prerequisite, not an entitlement for every local account. Credit a user-owned instance, not unrestricted access to another user's daemon. Preserve the selected persistent client-authorization files and revocation/restart policy; the API example does not replace them with an ephemeral-only configuration. Directory dependencies and incomplete Conflux implementation remain separate findings. No new Tor service was published.
Public sources
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round240-sources.json