Skip to main content
config.toml schema, environment variables, override layering, and the mxnode config commands.

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:
  1. CLI flagsmxnode upgrade --binary-tag v1.11.5 beats anything in the file.
  2. User config~/.config/mxnode/config.toml.
  3. System config/etc/mxnode/config.toml.
  4. Built-in defaults — compiled into mxnode-config.
Inspect what won where:
Each leaf is annotated default, system, user, or flag.

Auto-created config

On the first state-changing command:
Auto-detected $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:
Tokens are never written to disk by mxnode.

Inspecting config

Modifying config

config set round-trips through toml_edit, so operator comments and section ordering are preserved.

Validation

Artifact source

Controls how mxnode install and mxnode upgrade acquire binaries:

Running from a fork

mxnode then resolves tags from 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