Configuration

Server Timezone

Make sure UTC is set as the server timezone. Use the timedatectl command to find out what timezone you are currently in.

danger

⚠️WARNING: Ensure that UTC is set as the server timezone. A LastResultsHash mismatch problem could be brought on by a different timezone configuration. Your node will go offline because of this!

Block Time

When committing a block, the timeout-commit value in the node configuration determines how long we wait before moving on to the new height (this gives us a chance to get some more pre-commits even though we already have +2/3). 5s is the current default value.

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 ~/.humasd/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 = "5s"

Peers

In ~/.humansd/config/config.toml you can configure your peers.

For an automated method, see the Add persistent peers section in our documentation; nevertheless, the field should resemble the following (do not duplicate this, this is just an example):

persistent_peers = "1c8629b474c9e0f0b24e81684992448963cf8d11@65.109.84.103:26656,42f95015c31c7814b6a0a717fd8c63d15f896e88@94.237.27.19:26656,787cebc84a0750f6625512a39b39c366ddc13f5c@65.109.92.235:26656,ceba57f1376d4949cc0419918d110f0085b24b25@135.181.113.225:26656,ca1e46048e4a9b65d60bc9e749aa431401f34ed7@144.76.45.59:26656,b1f13e9971cfdcf784fb0efbd1b72417d5410a02@195.201.59.194:26656,ce7eddddd4bfd1c47f995f745d409554b2361075@202.61.236.219:26656,e6489cf86b51fa37cae968ccbbda1da03b742a5e@128.140.56.206:26656,acce1a823a281b371bb9167180f9c80422071ece@143.110.190.223:26656,8c3c25fa9cd6289d0342cf0e42916f381a1fd671@78.46.64.59:26656,34fd880f1bf2eb7b7481436d0746bbc05a4a5805@144.76.97.35:26656,36f956fa2fe317a5d3163d0b6c7b104e33aa62e9@103.180.28.79:26656,69a6d587d4bd0d9f37404dbc03029c6220bde175@81.30.157.35:19656,b52e0c6553fb42b5899b93dd584959db2bb23422@95.217.200.36:26656,c6a6967cceb8fd5df06519eb326b78b44c924ebf@85.239.233.20:26656,c94e42eec8bcc7f6db81748a97e5f10d59710e95@135.181.138.160:26656,5b92ede5e88c5029d6c7b3b360b9cf59051ce409@65.109.84.33:26656,86768c62c83fcdeb54514b33b33ab44fd9fa5c05@49.13.9.135:26656,62faee4c6224b3562d7123acea58180021c8b47b@162.55.173.57:26656,6f6a90701f3cc459a9007456fa84abf647a68ef5@159.69.69.183:26656,b1639fb460c9f55bb3acc3006df64ac5013f1412@91.194.30.203:26656,497886715ac23475f7428bd177b9fa53ff886a8d@78.46.80.79:26656,b9767aa2312748caaf67425890768d85186b69b1@5.9.87.205:26646,5e1f23a66fafd1a73871f055a6dd2165c01fe1c2@65.109.25.62:26656,8d5e7c030a4790b2caba38520d167c1ab2bc1244@51.79.82.138:26656,0844b9e6e2cb9c7d7a3eaa037f9e16ac66c9005c@5.161.64.185:26656,9da3f749f0b9b5180399d2099e9cb4f7b5d2ccaf@85.239.240.45:26656,d5519e378247dfb61dfe90652d1fe3e2b3005a5b@65.109.68.190:22656,946b549550e9c564193bf4c963d84b17e5415a50@136.243.136.241:26656,8258f82e1eb92203af5aa017e90baed4b84a5c46@135.181.142.117:26656"

Sharing your Peer

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

humansd tendermint show-node-id
cd36e32e0b5585356048a4481d16c12f69c3f69c

• Peer Format: node-id@ip:port
• Example: cd36e32e0b5585356048a4481d16c12f69c3f69c@153.196.214.123:26656

Healthy peers

Increase the following parameters in the config.toml file if you only have one seed node and few or no persistent peers:

# Maximum number of inbound peers
max_num_inbound_peers = 40

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