Configuration

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 "1s".
# In blockxd/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 = "1s"
Peers
In blockx/config/config.toml you can set your peers.
This should be replaced with mainnet validators after mainnet launch
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,7a[email protected]:26656"
Sharing your Peer
You can see and share your peer with the tendermint show-node-id command
blockxd tendermint show-node-id ac29d21d0a6885465048a4481d16c12f59b2e58b
Peer Format: node-id@ip:port
Example: [email protected]:26656
Healthy peers
If you are relying on just 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
Run a Validator
Disk Usage Optimization
Last modified 1mo ago