Configuration

Server Timezone

Ensure that your server's timezone is set to UTC. To check your current timezone configuration, execute the following command:

timedatectl

Warning 🚨 IMPORTANT: Configuring a different timezone may result in a LastResultsHash mismatch error, which can cause your node to become non-operational.

---

Block Time

The timeout-commit parameter in the node configuration determines the waiting period after committing a block before starting the next height. This delay allows additional pre-commits to be received, even if the required +2/3 threshold has already been met. The default value is set to "3s".

Note: Starting from version 6, this setting is managed automatically by the server during node initialization. Validators must verify their local node configurations to optimize the network for approximately 4-second block times.

Configuration File: ~/.dhived/config/config.toml

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

# Duration to wait after committing a block before starting the next height.
# Allows additional pre-commits to be received.
timeout_commit = "3s"

---

Peers

In the ~/.dhived/config/config.toml file, you can configure your peers.

Refer to the Add Persistent Peers section in the documentation for automated setup. The persistent_peers field should be a comma-separated list of peers. Example format (do not copy directly):

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

Sharing Your Peer

To retrieve and share your node ID, use the following command:

dhived tendermint show-node-id

Example output:

ac29d21d0a6885465048a4481d16c12f59b2e58b

Peer Format: node-id@ip:port

Example:

[email protected]:26656

Healthy Peers

If your node relies only on a seed node or has a low number of persistent peers, increase the following parameters in config.toml to improve connectivity:

# Maximum number of inbound peers
max_num_inbound_peers = 120

# Maximum number of outbound peers (excluding persistent peers)
max_num_outbound_peers = 60

---

EIP-155 Replay Protection

The EIP-155 replay protection is globally enabled within the EVM module parameters. If this feature is disabled as a global requirement, node operators can enable support for unprotected transactions by modifying the relevant setting in the node configuration file:

Configuration File: $HOME/.dhived/config/config.toml

# Allows unprotected (non EIP-155 signed) transactions via the node's RPC when the global parameter is disabled.
allow-unprotected-txs = true  # Default is false

Ensure proper configuration to maintain network security and integrity.