cronostestnet_338-3
.cronos_0.7.0-rc1
upgrade:~/.cronos/config/app.toml
(given there are some new parameter introduced in the upgrade), either by manually replace the local app.toml
with this new app.toml, or by:1553700
;cronos_0.7.0-rc2
upgrade:1869000
;cronos_0.7.0-rc3
upgrade:cronosd
bycronosd
cronostestnet_338-2
before, you would have to clean up the old blockchain data and start over again, it can be done by running:cronosd
moniker
will be the displayed id of your node when connected to the Cronos network. When providing the moniker value, make sure you drop the square brackets since they are not needed. The example below shows how to initialize a node named pegasus-node
:~/.cronos/
for illustration.cronosd
to your binary path and run it by cronosd
genesis.json
by:genesis.json
. You should see OK!
if the sha256sum checksum matches.sha256sum
was not installed by default. In this case, you may setup sha256sum
with this command:~/.cronos/config/app.toml
, update minimum gas price to avoid transaction spamming​~/.cronos/config/config.toml
, validator nodes need to modify the configurations of persistent_peers
, create_empty_blocks_interval
and timeout_commit
. For non-validator full nodes, only persistent_peers
modification is required:jq
is missing, you may install it by: brew install jq
cronosd
has been configured, we are ready to start the node and sync the blockchain data.too many files opened...
, then you need to set a higher number for maximum open file descriptors in your OS.false
, It means that your node is fully synced; otherwise, it returns true
and implies your node is still catching up.