Document relay and mDNS direction
This commit is contained in:
parent
ebc40ed208
commit
8334cc5e00
3 changed files with 24 additions and 3 deletions
|
|
@ -74,6 +74,21 @@ geth-to-geth connections without granting trust from discovery alone.
|
|||
- Endpoint identity is bound to agent/node identity in local metadata.
|
||||
- Restarting the daemon preserves higher-level node identity.
|
||||
|
||||
- `[ ]` Relay policy and configuration.
|
||||
Acceptance criteria:
|
||||
- Config can select disabled, default Iroh relays, staging relays, and future
|
||||
custom relay maps.
|
||||
- The intended product default uses relays unless explicitly disabled.
|
||||
- `geth status --json` reports the selected relay mode.
|
||||
- Tests cover config parsing and endpoint builder relay-mode selection.
|
||||
|
||||
- `[ ]` LAN mDNS discovery.
|
||||
Acceptance criteria:
|
||||
- The daemon can advertise and discover local geth peer cards over mDNS.
|
||||
- mDNS results are stored only as untrusted peer candidates.
|
||||
- Discovered EndpointIDs do not grant module access without keychain/auth
|
||||
validation.
|
||||
|
||||
- `[ ]` Protocol/router scaffold.
|
||||
Acceptance criteria:
|
||||
- ALPN constants are registered through one module router.
|
||||
|
|
|
|||
Loading…
Reference in a new issue