Skip to main content

Configuration

Server Timezone​

Make sure your server timezone configuration is UTC. To know what is your current timezone, run the timedatectl command.

danger

🚨 DANGER: Having a different timezone configuration may cause a LastResultsHash mismatch error. This will take down your node!

Block Time​

The timeout-commit value in the node config defines how long we wait after committing a block, before starting on the new height (this gives us a chance to receive some more pre-commits, even though we already have +2/3). The current default value is "3s".

tip

Note: From v6, this is handled automatically by the server when initializing the node. Validators will need to ensure their local node configurations in order to speed up the network to ~4s block times.

# In ~/.evmosd/config/config.toml

#######################################################
###         Consensus Configuration Options         ###
#######################################################
[consensus]

### ... 

# How long we wait after committing a block, before starting on the new
# height (this gives us a chance to receive some more precommits, even
# though we already have +2/3).
timeout_commit = "3s"

Peers​

In ~/.evmosd/config/config.toml you can set your peers.

See the Add persistent peers section in our docs for an automated method, but field should look something like a comma separated string of peers (do not copy this, just an example):

persistent_peers = "[email protected]:24656,[email protected]:26656,[email protected]:26656,[email protected]:26656,[email protected]:26656,[email protected]:26656,[email protected]:26656,[email protected]:26656,[email protected]:26656,[email protected]:26656,[email protected]:26656"

Sharing your Peer​

You can see and share your peer with the tendermint show-node-id command

evmosd tendermint show-node-id
ac29d21d0a6885465048a4481d16c12f59b2e58b

Healthy peers​

If you are relying on just a seed node and no persistent peers or a low amount of them, please increase the following params in the config.toml:

# Maximum number of inbound peers
max_num_inbound_peers = 120

# Maximum number of outbound peers to connect to, excluding persistent peers
max_num_outbound_peers = 60

EIP-155 Replay Protection​

The EIP-155 replay protection is enabled globally in the EVM module parameters. In case this is disabled as a global requirement, node operators can opt into supporting unprotected transactions by adjusting the corresponding setting in the node configuration:

# in $HOME/.evmosd/config/config.toml

# AllowUnprotectedTxs restricts unprotected (non EIP-155 signed) transactions to be submitted via
# the node's RPC when the global parameter is disabled.
allow-unprotected-txs = true  # false by default

More information about EIP-155 can be found here: EIP-155: Replay Protection.