Shortest commands
mxnode reads a layered configuration. The config file lives at ~/.config/mxnode/config.toml (auto-created on first use); a system-wide /etc/mxnode/config.toml is also honored. CLI flags override both.
Resolution order
Highest-precedence layer wins:- CLI flags —
mxnode upgrade --binary-tag v1.11.5beats anything in the file. - User config —
~/.config/mxnode/config.toml. - System config —
/etc/mxnode/config.toml. - Built-in defaults — compiled into
mxnode-config.
default, system, user, or flag.
Auto-created config
On the first state-changing command:$USER / $HOME come from $USER → $LOGNAME → $HOME (in that order).
Full schema
Path placeholders
[paths] values support these placeholders:
Environment variables
Only one is read:Inspecting config
Modifying config
config set round-trips through toml_edit, so operator comments and section ordering are preserved.
Validation
Artifact source
Controls howmxnode install and mxnode upgrade acquire binaries:
Running from a fork
https://api.github.com/repos/your-org/mx-chain-go/releases and clones from https://github.com/your-org/mx-chain-go.git.
Sample configs
- Multikey primary, mainnet
- Observer squad on a fork
- Testnet observer with custom log level

