Using Ansible

This section guides you through starting and running the validator node through an Ansible playbook.

For the system requirements, see Validator Node System Requirements.

If you would like to start and run the validator node from binaries, see the guide on spinning up a Validator node using binaries.

Caution

There is limited space for accepting new validators. New validators can only join the active set when an already active validator unbonds.

Prerequisites¶

Three machines — one local machine on which you will run the Ansible playbook; two remote machines — one sentry and one validator.
On the local machine, Ansible installed.
On the local machine, Python 3.x installed.
On the remote machines, make sure Go is not installed.
On the remote machines, your local machine’s SSH public key is on the remote machines to let Ansible connect to them.
We have Bloxroute available as a relay network. If you need a gateway to be added as your Trusted Peer please contact @validator-support-team in Polygon Discord > POS VALIDATORS | FULL NODE PROVIDERS | PARTNERS > bloxroute.

Overview¶

Caution

You must follow the exact outlined sequence of actions, otherwise you will run into issues. For example, a sentry node must always be set up before the validator node.

To get to a running validator node, do the following:

Have the three machines prepared.
Set up a sentry node through Ansible.
Set up a validator node through Ansible.
Configure the sentry node.
Start the sentry node.
Configure the validator node.
Set the owner and signer keys.
Start the validator node.
Check node health with the community.

Set up the Sentry node¶

On your local machine, clone the node-ansible repository:

git clone https://github.com/maticnetwork/node-ansible

Change to the cloned repository:

cd node-ansible

Add the IP addresses of the remote machines that will become a sentry node and a validator node to the inventory.yml file.

all:
  hosts:
  children:
    sentry:
      hosts:
        xxx.xxx.xx.xx: # <----- Add IP for sentry node
        xxx.xxx.xx.xx: # <----- Add IP for second sentry node (optional)
    validator:
      hosts:
        xxx.xxx.xx.xx: # <----- Add IP for validator node

Example:

all:
  hosts:
  children:
    sentry:
      hosts:
        188.166.216.25:
    validator:
      hosts:
        134.209.100.175:

Check that the remote sentry machine is reachable. On the local machine, run:

$ ansible sentry -m ping

You should get this as output:

xxx.xxx.xx.xx | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python3"
    },
    "changed": false,
    "ping": "pong"
}

Do a test run of the sentry node setup:

ansible-playbook -l sentry playbooks/network.yml --extra-var="bor_version=v1.1.0 heimdall_version=v1.0.3  network_version=mainnet-v1 node_type=sentry/sentry heimdall_network=mainnet" --list-hosts

This will be the output:

playbook: playbooks/network.yml
  pattern: ['all']
  host (1):
    xx.xxx.x.xxx

Run the sentry node setup with sudo privileges:

ansible-playbook -l sentry playbooks/network.yml --extra-var="bor_version=v1.1.0 heimdall_version=v1.0.3  network_version=mainnet-v1 node_type=sentry/sentry heimdall_network=mainnet" --ask-become-pass

Once the setup is complete, you will see a message of completion on the terminal.

Note

If you run into an issue and would like to start over, run:

ansible-playbook -l sentry playbooks/clean.yml

Set up the Validator node¶

At this point, you have the sentry node set up.

On your local machine, you also have the Ansible playbook set up to run the validator node setup.

Check that the remote validator machine is reachable. On the local machine, run ansible validator -m ping.

You should get this as output:

xxx.xxx.xx.xx | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python3"
    },
    "changed": false,
    "ping": "pong"
}

Do a test run of the validator node setup:

ansible-playbook -l validator playbooks/network.yml --extra-var="bor_version=v1.1.0 heimdall_version=v1.0.3 network_version=mainnet-v1 node_type=sentry/validator heimdall_network=mainnet" --list-hosts

You should get this as output:

playbook: playbooks/network.yml
  pattern: ['all']
  host (1):
    xx.xxx.x.xxx

Run the validator node setup with sudo privileges:

ansible-playbook -l validator playbooks/network.yml --extra-var="bor_version=v1.1.0 heimdall_version=v1.0.3  network_version=mainnet-v1 node_type=sentry/validator heimdall_network=mainnet" --ask-become-pass

Once the setup is complete, you will see a message of completion on the terminal.

Note

If you run into an issue and would like to start over, run:

ansible-playbook -l validator playbooks/clean.yml

Configure the Sentry node¶

Log into the remote sentry machine.

Configure the Heimdall Service¶

Open config.toml for editing vi /var/lib/heimdall/config/config.toml.

Change the following:

moniker — any name. Example: moniker = "my-full-node".
seeds — the seed node addresses consisting of a node ID, an IP address, and a port.

Should already have the following values:

seeds="1500161dd491b67fb1ac81868952be49e2509c9f@52.78.36.216:26656,dd4a3f1750af5765266231b9d8ac764599921736@3.36.224.80:26656,8ea4f592ad6cc38d7532aff418d1fb97052463af@34.240.245.39:26656,e772e1fb8c3492a9570a377a5eafdb1dc53cd778@54.194.245.5:26656,6726b826df45ac8e9afb4bdb2469c7771bd797f1@52.209.21.164:26656"

pex — set the value to true to enable the peer exchange. Example: pex = true.
private_peer_ids — the node ID of Heimdall set up on the validator machine.

To get the node ID of Heimdall on the validator machine:

Log into the validator machine.
Run heimdalld tendermint show-node-id.

Example: private_peer_ids = "0ee1de0515f577700a6a4b6ad882eff1eb15f066".

prometheus — set the value to true to enable the Prometheus metrics. Example: prometheus = true.
max_open_connections — set the value to 100. Example: max_open_connections = 100.

Save the changes in config.toml.

Configure the Bor Service¶

Open for editing vi /var/lib/bor/config.toml.

In config.sh, ensure the boot node addresses consisting of a node ID, an IP address, and a port by the bootnode paramater:

bootnodes "enode://b8f1cc9c5d4403703fbf377116469667d2b1823c0daf16b7250aa576bacf399e42c3930ccfcb02c5df6879565a2b8931335565f0e8d3f8e72385ecf4a4bf160a@3.36.224.80:30303", "enode://8729e0c825f3d9cad382555f3e46dcff21af323e89025a0e6312df541f4a9e73abfa562d64906f5e59c51fe6f0501b3e61b07979606c56329c020ed739910759@54.194.245.5:30303"

Save the changes in config.toml.

Open for editing vi /var/lib/bor/config.toml.

In config.toml, ensure the static-nodes parameter has the following values:

"enode://validator_machine_enodeID@validator_machine_ip:30303" — the node ID and IP address of Bor set up on the validator machine.

To get the node ID of Bor on the validator machine:

Log into the validator machine.
Run bor bootnode -node-key /var/lib/bor/data/bor/nodekey, this command only works while Bor is not running. If the IP address is 0.0.0.0 then replace it with external facing IP address.

Save the changes in config.toml.

Configure firewall¶

The sentry machine must have the following ports open to the world 0.0.0.0/0:

26656- Your Heimdall service will connect your node to other nodes using the Heimdall service.
30303- Your Bor service will connect your node to other nodes using the Bor service.
22- Open this port if your node is servicing validators. You will likely want to restrict what traffic can access this port as it is a sensitive port.

Note

However, if they use a VPN connection, they can allow incoming SSH connections only from the VPN IP address.

Start the sentry node¶

You will first start the Heimdall service. Once the Heimdall service syncs, you will start the Bor service.

Note

The Heimdall service takes several days to fully sync from scratch.

Alternatively, you can use a maintained snapshot, which will reduce the sync time to a few hours. For detailed instructions, see Snapshot Instructions for Heimdall and Bor.

For snapshot download links, see Polygon Chains Snapshots.

Start the Heimdall service¶

The latest version, Heimdall v1.0.3, contains a few enhancements such as: 1. Restricting data size in state sync txs to: * 30Kb when represented in bytes * 60Kb when represented as string. 2. Increasing the delay time between the contract events of different validators to ensure that the mempool doesn’t get filled very quickly in case of a burst of events which can hamper the progress of the chain.

The following example shows how the data size is restricted:

Data - "abcd1234"
Length in string format - 8
Hex Byte representation - [171 205 18 52]
Length in byte format - 4

Start the Heimdall service:

sudo service heimdalld start

Check the Heimdall service logs:

journalctl -u heimdalld.service -f

Note

In the logs, you may see the following errors:

Stopping peer for error
MConnection flush failed
use of closed network connection

These mean that one of the nodes on the network refused a connection to your node. You do not need to do anything with these errors. Wait for your node to crawl more nodes on the network.

Check the sync status of Heimdall:

curl localhost:26657/status

In the output, the catching_up value is:

true — the Heimdall service is syncing.
false — the Heimdall service is fully synced.

Wait for the Heimdall service to fully sync.

Start the Bor Service¶

Once the Heimdall service is fully synced, start the Bor service.

Start the Bor service:

sudo service bor start

Check the Bor service logs:

journalctl -u bor.service -f

Configure the validator node¶

Note

To complete this section, you must have your own RPC endpoint of your own fully synced Ethereum mainnet node ready. The use of Infura and Alchemy is also sufficient and widely used among validators.

Configure the Heimdall Service¶

Log into the remote validator machine.

Open config.toml for editing vi /var/lib/heimdall/config/config.toml.

Change the following:

moniker — any name. Example: moniker = "my-validator-node".
pex — set the value to false to disable the peer exchange. Example: pex = false.
private_peer_ids — comment out the value to disable it. Example: # private_peer_ids = "".

To get the node ID of Heimdall on the sentry machine:

Login to the sentry machine.
Run heimdalld tendermint show-node-id.

Example: persistent_peers = "sentry_machineNodeID@sentry_instance_ip:26656"

prometheus — set the value to true to enable the Prometheus metrics. Example: prometheus = true.

Save the changes in config.toml.

Open for editing vi /var/lib/heimdall/config/heimdall-config.toml.

In heimdall-config.toml, change the following:

eth_rpc_url — an RPC endpoint for a fully synced Ethereum mainnet node, i.e Infura. eth_rpc_url =<insert Infura or any full node RPC URL to Ethereum>

Example: eth_rpc_url = "https://nd-123-456-789.p2pify.com/60f2a23810ba11c827d3da642802412a"

Save the changes in heimdall-config.toml.

Configure the Bor Service¶

Open for editing vi /var/lib/bor/config.toml.

In config.toml, ensure the trusted-nodes parameter has the following values:

"enode://sentry_machine_enodeID@sentry_machine_ip:30303" — the node ID and IP address of Bor set up on the sentry machine.

To get the node ID of Bor on the sentry machine:

Log into the sentry machine.
Run bor bootnode -node-key /var/lib/bor/data/bor/nodekey, this command only works while Bor is not running. If the IP address is 0.0.0.0, replace it with external facing IP address.

Save the changes in config.toml file.

Set the owner and signer key¶

Note

To complete this section, you must have already created two Ethereum wallets and have the private keys available as needed. One address will be used as the Signer and the other address as the Owner. Only the Signer address will be used in this section at the moment.

On Polygon, you should keep the owner and signer keys different.

Signer — the address that signs the checkpoint transactions. The recommendation is to keep at least 1 ETH on the signer address.
Owner — the address that does the staking transactions. The recommendation is to keep the MATIC tokens on the owner address.

Generate a Heimdall private key¶

You must generate a Heimdall private key only on the validator machine. Do not generate a Heimdall private key on the sentry machine.

To generate the private key, run:

heimdallcli generate-validatorkey ETHEREUM_PRIVATE_KEY

Note

ETHEREUM_PRIVATE_KEY — your Ethereum wallet’s Signer private key

This will generate priv_validator_key.json. Move the generated JSON file to the Heimdall configuration directory:

mv ./priv_validator_key.json /var/lib/heimdall/config/

Generate a Bor keystore file¶

You must generate a Bor keystore file only on the validator machine. Do not generate a Bor keystore file on the sentry machine.

To generate the private key, run:

heimdallcli generate-keystore ETHEREUM_PRIVATE_KEY

Note

ETHEREUM_PRIVATE_KEY — your Ethereum wallet’s Signer private key.

When prompted, set up a password to the keystore file.

This will generate a UTC-<time>-<address> keystore file.

Move the generated keystore file to the Bor configuration directory:

mv ./UTC-<time>-<address> /var/lib/bor/data/keystore/

Ensure the keystore parameter in /var/lib/bor/config.toml matches the directory /var/lib/bor/data/keystore/

Add `password.txt`¶

Make sure to create a password.txt file then add the Bor keystore file password right in the /var/lib/bor/password.txt file.

Ensure that password parameter in /var/lib/bor/config.toml matches the location of the password file.

Add your Ethereum address¶

Open for editing vi /var/lib/bor/config.toml.

In [accounts] section you should have paramater password already defined from previous step, now add your Ethereum address to unlock parameter and also ensure allow-insecure-unlock has a value of true.

Example:

 [accounts]
    allow-insecure-unlock = true
    password = "/var/lib/bor/password.txt"
    unlock = ["0xca67a8D767e45056DC92384b488E9Af654d78DE2"]

Save the changes in /var/lib/bor/config.toml.

Start the Validator node¶

At this point, you must have:

The Heimdall service on the sentry machine fully synced and running.
The Bor service on the sentry machine running.
The Heimdall service and the Bor service on the validator machine configured.
Your owner and signer keys configured.

Start the Heimdall Service¶

You will now start the Heimdall service on the validator machine. Once the Heimdall service syncs, you will start the Bor service on the validator machine.

Start the Heimdall service:

sudo service heimdalld start

Check the Heimdall service logs:

journalctl -u heimdalld.service -f

Check the sync status of Heimdall:

curl localhost:26657/status

In the output, the catching_up value is:

true — the Heimdall service is syncing.
false — the Heimdall service is fully synced.

Wait for the Heimdall service to fully sync.

Start the Bor Service¶

Once the Heimdall service on the validator machine is fully synced, start the Bor service on the validator machine.

Start the Bor service:

sudo service bor start

Check the Bor service logs:

journalctl -u bor.service -f

Seed nodes and bootnodes¶

Heimdall seed nodes:

moniker=<enter unique identifier>

# Mainnet:
seeds="1500161dd491b67fb1ac81868952be49e2509c9f@52.78.36.216:26656,dd4a3f1750af5765266231b9d8ac764599921736@3.36.224.80:26656,8ea4f592ad6cc38d7532aff418d1fb97052463af@34.240.245.39:26656,e772e1fb8c3492a9570a377a5eafdb1dc53cd778@54.194.245.5:26656,6726b826df45ac8e9afb4bdb2469c7771bd797f1@52.209.21.164:26656"

# Testnet:
seeds="9df7ae4bf9b996c0e3436ed4cd3050dbc5742a28@43.200.206.40:26656,d9275750bc877b0276c374307f0fd7eae1d71e35@54.216.248.9:26656,1a3258eb2b69b235d4749cf9266a94567d6c0199@52.214.83.78:26656"

Tip

The following Heimdall seed can be used for both mainnet and Mumbai testnet: 8542cd7e6bf9d260fef543bc49e59be5a3fa9074@seed.publicnode.com:27656

Bootnodes:

# Mainnet:
bootnode ["enode://b8f1cc9c5d4403703fbf377116469667d2b1823c0daf16b7250aa576bacf399e42c3930ccfcb02c5df6879565a2b8931335565f0e8d3f8e72385ecf4a4bf160a@3.36.224.80:30303", "enode://8729e0c825f3d9cad382555f3e46dcff21af323e89025a0e6312df541f4a9e73abfa562d64906f5e59c51fe6f0501b3e61b07979606c56329c020ed739910759@54.194.245.5:30303"]

# Testnet:
bootnodes ["enode://bdcd4786a616a853b8a041f53496d853c68d99d54ff305615cd91c03cd56895e0a7f6e9f35dbf89131044e2114a9a782b792b5661e3aff07faf125a98606a071@43.200.206.40:30303", "enode://209aaf7ed549cf4a5700fd833da25413f80a1248bd3aa7fe2a87203e3f7b236dd729579e5c8df61c97bf508281bae4969d6de76a7393bcbd04a0af70270333b3@54.216.248.9:30303"]

Check node health with the community¶

Now that your Sentry and Validator nodes are synced and running, head over to Discord and ask the community to health-check your nodes.

Note

As validators, it’s mandatory to always have a check of the signer address. If the ETH balance reaches below 0.5 ETH then it should be refilled. Avoiding this will push out nodes from submitting checkpoint transactions.

Proceed to staking¶

Now that you have your Sentry and Validator nodes health-checked, proceed to Staking.

Using Ansible

Prerequisites¶

Overview¶

Set up the Sentry node¶

Set up the Validator node¶

Configure the Sentry node¶

Configure the Heimdall Service¶

Configure the Bor Service¶

Configure firewall¶

Start the sentry node¶

Start the Heimdall service¶

Start the Bor Service¶

Configure the validator node¶

Configure the Heimdall Service¶

Configure the Bor Service¶

Set the owner and signer key¶

Generate a Heimdall private key¶

Generate a Bor keystore file¶

Add password.txt¶

Add your Ethereum address¶

Start the Validator node¶

Start the Heimdall Service¶

Start the Bor Service¶

Seed nodes and bootnodes¶

Check node health with the community¶

Proceed to staking¶

Comments

Add `password.txt`¶