Basel (v2.4.0-bkc)

Before Upgrading

• This upgrade may involve some downtime. Please ensure you have a maintenance plan in place before proceeding with the following upgrade instructions.

• During the upgrade, your Geth (go-ethereum) node will be temporarily unavailable to the KUB network.

• After upgrading to the new version, your node may take approximately 5 to 15 minutes to resynchronize with the latest blockchain information.

• We strongly recommend creating a disk snapshot before upgrading to prevent any potential data loss during the process.

Instructions

Ensure the Geth node is fully stopped before proceeding with the upgrade

systemctl stop geth

Download and extract the Geth v2.4.0 binary from the official GitHub releases

wget https://github.com/kub-chain/bkc/releases/download/v2.4.0-bkc/geth2.4.0.linux-amd64.tar.gz
tar -xvf ./geth2.4.0.linux-amd64.tar.gz -c /usr/bin/

Grant the necessary execution permissions to the downloaded binary

sudo chmod +x /usr/bin/geth

Confirm that the correct version has been installed

/usr/bin/geth version

The expected output must be: v2.4.0-bkc-stable

Geth
Version: 2.4.0-bkc-stable
Git Commit: 28cb5603e9c866a0ff67c5e0520274adf819402a # This may be different
Git Commit Date: 20260303 # This may be different
...

Retrieve the latest genesis.json via the following command

wget https://raw.githubusercontent.com/kub-chain/bkc-node/main/mainnet/genesis.json

Verify that the downloaded file contains the required hard fork configuration

cat ./genesis.json

The output should contain the following field:

{
  ...
  "baselBlock": {
      "block": 31237946,
      "superNode": "0xcf723fE5a8118efE70D3fAdd56C5e6D01aDeC7A3",
      "superNodeOwner": "0x5106ffca7cC44E6cFfEE9bD016A0934130b0322f",
      "period": 3
  },
  ...
}

Apply the new genesis.json

/usr/bin/geth --datadir /bkc-node/mainnet/data init ./genesis.json

The data directory path used in the guide may differ from your actual environment. Verify your data directory path before executing any command and substitute it accordingly.

Start the Geth service to resume normal operation

systemctl start geth

Monitor the output logs to confirm the node has started successfully and is operating as expected

journalctl -fu geth