Hello everyone,
Earlier, cLabs submitted a governance proposal to bump the minimum client version to v1.0.1 to enforce a critical security fix. However, through our conversations with node operators, developers, and partners, we have realized that some community members are not ready to upgrade their nodes within the short timeline. In order to prevent unexpected interruptions to services and operations that depend on the Celo network, cLabs has recommended approvers not to approve. In the case that this proposal is approved, cLabs recommends the community to delay this proposal by voting “NO”. When more stakeholders have upgraded their nodes, cLabs will re-introduce this proposal.
If you have not upgraded your celo-blockchain software to v1.0.1, please do so ASAP, by following these steps:
- Stop and kill your node container
- Pull the latest image
- Start the node container
Note that you do not need to re-sync the chain data. Also, if you know someone who’s still running on the older version, please remind them to upgrade!
If you are not familiar with the CLI, here are the commands for updating the image of a full node:
export CELO_IMAGE=us.gcr.io/celo-org/celo-node:mainnet
export NETWORK_ID=42220
docker stop celo-fullnode & docker rm celo-fullnode
docker pull $CELO_IMAGE
cd celo-data-dir
docker run --name celo-fullnode -d --restart unless-stopped -p 127.0.0.1:8545:8545 -p 127.0.0.1:8546:8546 -p 30303:30303 -p 30303:30303/udp -v $PWD:/root/.celo $CELO_IMAGE --verbosity 3 --networkid $NETWORK_ID --syncmode full --rpc --rpcaddr 0.0.0.0 --rpcapi eth,net,web3,debug,admin,personal --light.serve 90 --light.maxpeers 1000 --maxpeers 1100 --etherbase $CELO_ACCOUNT_ADDRESS --bootnodes $BOOTNODE_ENODES --nousb
You can refer to the documentation here for full nodes and here for validators.
The cLabs Team