S04-CJ: Yes
Rationale
The pinned route server reads participant-supplied configuration, starts its own HTTP/WebSocket service, optionally connects to the local cjdns router, and connects to the explicit config.peers list. The example's numeric server address is configurable, not a fixed operational authority. Combined with the selected local node keys and private numeric peer credentials, participants can administer the required routing and replication roles themselves.
Assessment method
Source and protocol dependency review; no runtime execution
Source context
Pinned cjdns route-server source and RFC 1034
Outstanding qualification
This is a dependency finding for the selected route-server design, not a return to a DHT-only profile. E03-CJ and the client/server version-binding and interoperability qualifications remain open. The source comment recommending an existing scanning server is not a protocol requirement; no scanner or network process was started.
Public sources
- https://github.com/CJDNS-Development-Team/CJDNS/blob/46c9c1b6828f746f00733c10d8e82c5295107514/cjdns-snode/src/server.rs
- https://github.com/CJDNS-Development-Team/CJDNS/blob/46c9c1b6828f746f00733c10d8e82c5295107514/cjdns-snode/src/main.rs
- https://github.com/CJDNS-Development-Team/CJDNS/blob/46c9c1b6828f746f00733c10d8e82c5295107514/cjdns-snode/config.example.json
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round253-sources.json
- round215.html