Run a leader to accept application transactions, synchronize accounts with the base chain, settle state, and run recurring tasks. It uses Engine to execute transactions, store state, and replicate to allowed followers.
Prepare a configuration using the leader example. Replace sample identities and provider credentials, choose storage and listener addresses, and supply the configured program executable files.
From the workspace root:
cargo run --release --locked -p magicblock-validator -- config.tomlThe configuration path is positional. Command-line setting overrides take
precedence over environment variables, which override the TOML file. See
configuration for details, or append
--help for available options.
Fund the signing identity before starting: setup can submit base-chain transactions to initialize and delegate fee vaults. Without a configuration file, the leader connects to devnet; it does not start a local base chain. Domain registration is separate: use the operator CLI.
To let a verifier follow this leader, add its local public identity to
engine.replication.allowed-followers. An empty list allows no followers.
If a managed service exits unexpectedly, the process stops. Use its logs and metrics to investigate before restarting. For a replication follower without application services, run the verifier.
See deployment prerequisites and recovery for multi-host operation.