Structs§
- Config
- Config
Defaults - Minimal set of default values that a plugin can supply for core runtime parameters (only applied when the user has not explicitly set them).
- Config
Locks - Hard overrides for configuration fields. These represent values the
application developer wants to bake into the binary. Use together with
LockConflictPolicyto control whether external config may differ. - Discovery
Config - Encryption
Config - Encryption
Noise Config - Encryption
Paths - Logging
Config - Network
Config - Network
Persistence Config - Node
Config - Node
Locks - Realm
Access Config - Realm-scoped policy (optional) for peer type admission. Developers may define their own node types for a given realm (e.g., “daemon”, “admin”, “worker”). If set, remote peers MUST advertise a node_type present in this allow-list; otherwise the connection is rejected.
- Relay
Config - Simple
Hardcoded - A simple facade for declaring hardcoded values with an
overridableflag, mirroring the user’s mental model: “key => { value, overridable }”. - Trust
Policy Config - Trust
Policy Paths Config
Enums§
- Lock
Conflict Policy - Policy for how to handle conflicts when a locked value differs from a value provided via external configuration (e.g., file/env/cli).