Usage

Configuration-driven startup

The binary reads a JSON configuration through global --config. The implemented startup command is start; config-validate validates the selected file. init-config writes ./weave-dht.config.json. The separate init command prints “not implemented” and exits with status 1.

weave-dht-daemon --help
weave-dht-daemon init-config
weave-dht-daemon --config ./weave-dht.config.json config-validate

Review the generated file before starting. Its sample requests mTLS and references certificate files; it is not a ready-to-run deployment credential set. The daemon consumes node.listenAddrs, node.bootstrapPeers, storage path/cap/TTL values, and API listen/authentication/TLS fields. Several additional fields in the sample are not mapped by the daemon structs, so the JSON schema's acceptance is not proof that every setting affects this runtime.

After configuring the listener, storage, authentication and transport certificates, start with:

weave-dht-daemon --config ./weave-dht.config.json start

Bearer mode requires a non-empty WEAVE_DHT_ADMIN_BEARER. mTLS mode requires TLS support plus the actual certificate, private key, and client CA configuration. The --listen, --storage, --bootstrap, --rpc-addr, and companion weave-dht-daemon-cli commands are not this parser's interface.

Source: network/weave-dht-daemon/src/main.rs (Cli, Commands, DaemonConfig, startup and authentication construction). Package reference.