Skip to main content
mxnode install accepts a small set of orthogonal flags that combine into every supported shape. Default is one validator, no squad, no proxy.

Shortest commands

# 1 validator
mxnode install

# 4-shard multikey squad (one node per shard)
mxnode install --role multikey

# 4-shard observer squad
mxnode install --role observer --squad
--squad is implicit for --role multikey and explicit for everyone else.

All flags

FlagDefaultEffect
--role validator|observer|multikeyvalidatorWhat kind of node. Drives key handling.
--squadoffPin 4 nodes to shards 0/1/2/metachain. Implicit for multikey.
--with-proxyoffAlso install the MultiversX proxy alongside the nodes. Rejected for --role multikey — proxies belong with observers, not signing nodes.
--count <N>1Number of nodes (without --squad). Each gets Shard::Auto. Rejected for multikey.
--keys-file <PATH>auto-detectMultikey: path to allValidatorsKeys.pem.
--backup [<N>]offMultikey: mark this host as a backup. Pass --backup for level 1, --backup 2 for backup-of-backup, etc.
--binary-tag <T>latestPin the mx-chain-go tag.
--config-tag <T>latestPin the mx-chain-mainnet-config tag.
--proxy-tag <T>latestPin the mx-chain-proxy-go tag (with --with-proxy).
--dry-runoffPrint the plan without doing anything.

Common shapes

ShapeCommandResult
Multikey squad (primary)mxnode install --role multikeyFour nodes signing for ~/VALIDATOR_KEYS/allValidatorsKeys.pem. Squad is implicit.
Multikey squad (backup)mxnode install --role multikey --backupSame allValidatorsKeys.pem; takes over signing if the primary fails. RedundancyLevel = 1.
Observer squadmxnode install --role observer --squadFour observers, one per shard. No keys to manage.
Observer squad + proxymxnode install --role observer --squad --with-proxyThe observing-squad gateway shape.
Single validatormxnode install --role validatorOperator drops node-0.zip into ~/VALIDATOR_KEYS/ before mxnode start.

Why multikey doesn’t take --squad

A multikey host signs for every BLS key in the bundle behind whichever observer is in the right shard. Anything other than one node per shard breaks the model — fewer leaves shards uncovered, more duplicates them. --role multikey is therefore a 4-shard squad:
CommandResult
mxnode install --role multikey4 nodes, shards 0/1/2/metachain. ✓
mxnode install --role multikey --squadSame. --squad is accepted as a no-op.
mxnode install --role multikey --count 3Rejected — multikey is by-design 4-node.
For other roles, --squad is the way to opt into the same 4-shard layout.

Backup machines

The --backup flag stamps Preferences.RedundancyLevel on every node in a multikey install. Both primary and backup must hold the byte-identical allValidatorsKeys.pem:
CommandRedundancyLevelMeaning
mxnode install --role multikey0Primary — signs unconditionally
mxnode install --role multikey --backup1Backup — takes over if the primary stops responding
mxnode install --role multikey --backup 22Backup-of-backup
mxnode install --role multikey --backup 33And so on
See multikey + redundancy for the full setup recipe.

What changes per role

AspectValidatorObserverMultikey
Key filenode-{i}.zip per nodeNone — auto-generated on first startallValidatorsKeys.pem distributed to every node
prefs.toml DestinationShardAsObserverUntouched (only with --squad)Pinned with --squadPinned
config.toml [DbLookupExtensions] Enabledfalsetruetrue
prefs.toml RedundancyLevelUntouchedUntouchedStamped (0 primary, 1+ backup)
mxnode keys checkVerifies zipsSkippedSkipped

Misuse rejections

mxnode rejects nonsensical combinations at parse time so you don’t waste a build:
CommandOutcome
mxnode install --squad --count 4clap conflict — --squad is 4-node
mxnode install --role multikey --count 3--count is rejected for --role multikey
mxnode install --role multikey --with-proxy--with-proxy is rejected for --role multikey (signing nodes shouldn’t co-host public RPC)
mxnode install --keys-file foo --role observer--keys-file only applies to --role multikey
mxnode install --backup --role observer--backup only applies to --role multikey
mxnode install --role multikey (no allValidatorsKeys.pem anywhere)multikey install requires allValidatorsKeys.pem