Configuration Reference

Configuration Reference

Everything lives in a single default.toml under /config (template: configs/default.toml). Most settings are also editable from the Config tab in the UI: scalar settings apply live; engine-level settings write the file and offer an Apply & restart button.

Sections

Section	What it does
[daemon]	API host/port, data_dir, auto-generated api_key.
[race]	Race engine (aggressive): ports, connection caps, choking.
[hoard]	Hoard engine (seeding): ports, upload slots, queue limits.
[auth]	username + bcrypt password_hash (login → returns api_key).
[race_drain]	Auto-purge of the race scratch disk by watermark.
[vpn_speedtest]	Periodic egress capacity check against a public iperf3 server.
[[engine]]	Extra engines for sharding (id + role + per-engine settings).

Credentials

• api_key ([daemon]) — the X-Api-Key header for the native /api/* API. If empty (or the old change-me-in-production), Hydra generates a random one on boot and writes it back.
• [auth] username / password_hash — the UI login. Empty password_hash on first boot → a random admin password is generated and printed once in the logs. Set your own with hydra hash-password <pw>.

Editing safely from the UI

The Config tab writes keys in place (comments preserved) and re-validates the whole file against the schema before saving, so a bad value is rejected (HTTP 400) instead of bricking the daemon. Array/table settings (e.g. proxy_v2_trusted_sources, passkey maps) are shown read-only in the generic editor — edit those in the file directly.

Advanced / networking keys

listen_port_proxy_v2, listen_addr_proxy_v2, proxy_v2_trusted_sources, socks5_outbound_host / _port — all opt-in, off by default. See Networking Modes.