Module config 

Structs

Config

ConfigDefaults

Minimal set of default values that a plugin can supply for core runtime parameters (only applied when the user has not explicitly set them).

ConfigLocks

Hard overrides for configuration fields. These represent values the application developer wants to bake into the binary. Use together with LockConflictPolicy to control whether external config may differ.

ConnectionPolicyConfig

Connection preference policy (ADR-0005 Phase 1).

DeliveryConfig

DiscoveryConfig

EncryptionConfig

EncryptionNoiseConfig

EncryptionPaths

LoggingConfig

NatConfig

Optional UPnP-IGD port mapping and NAT diagnostics configuration (ADR-0009).

NatTraversalConfig

NAT traversal and hole-punching configuration (ADR-0005).

NetworkConfig

NetworkPersistenceConfig

NodeConfig

NodeLocks

NoiseTrustPolicyConfig

RealmAccessConfig

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.

RelayConfig

SimpleHardcoded

A simple facade for declaring hardcoded values with an overridable flag, mirroring the user’s mental model: “key => { value, overridable }”.

TrustPolicyConfig

TrustPolicyPathsConfig

UdpConfig

UDP + Noise transport configuration (optional; opt-in, ADR-0004).

Enums

LockConflictPolicy

Policy for how to handle conflicts when a locked value differs from a value provided via external configuration (e.g., file/env/cli).