2,693,800, which requires the node operator to update their Cronos Mainnet binary
cronostestnet_338-3before, you would have to clean up the old blockchain data and start over again, it can be done by running:
monikerwill be the displayed id of your node when connected to Cronos Chain network.
genesis.json. You should see
OK!if the sha256sum checksum matches.
~/.cronos/config/app.toml, update minimum gas price to avoid transaction spamming
~/.cronos/config/config.toml, validator nodes need to modify the configurations of
timeout_commit. For non-validator full nodes, only
seedmodification is required:
crc10u5mgfflasrfj9s94mt8l9yucrt2gzhcyt5tsg. This will be the address for performing transactions.
cronosdhas been configured, we are ready to start the node and sync the blockchain data:
false, It means that your node is fully synced; otherwise, it returns
trueand implies your node is still catching up.