How to manage localnet nodes and validators
Add nodes, control validation, and inspect election membership on a localnet
Use additional localnet nodes to test synchronization, validator participation, and consensus behavior.
Removing a node deletes its localnet state. Removing an elected validator can disrupt consensus. Save a snapshot before changing topology, and wait for elected duties to end before removal.
Prerequisites
- A running localnet.
- Docker memory and disk allocations sufficient for the additional nodes, as described in the localnet requirements.
Manage participation
- Open Network → Nodes and select Add node.
- Enter a name and choose whether the new node participates as a validator. Confirm creation.
- Inspect synchronization and readiness before relying on the node.
- Use the node's validation controls to enter or leave validation. Inspect Network → Validators for current and next elected sets.
Node start/stop controls preserve its state. Removing an additional node deletes its state. The genesis validator cannot be removed through these controls.
acton localnet node dev add validator-b --validator
acton localnet status dev --jsonWithout --validator, the added node is a full node that does not participate in elections. Replace <NODE_ID> with the ID from the result or status. Enable or disable future participation:
acton localnet node dev enter-validation '<NODE_ID>'
acton localnet node dev leave-validation '<NODE_ID>'After the node leaves both the current and next elected sets, remove it:
acton localnet node dev remove '<NODE_ID>'Verify election membership
Entering validation enables election participation; it does not immediately elect the node. Leaving validation still requires serving its existing elected duties. Check the current and next sets before removal.
Last updated on