v2.2.0 - BKC Performance Improvement

Description

This release improves the performance of Bitkub Chain to support high throughput.

Changes

• e9158d0 - Send all entire transactions and blocks to connected peers.
• 67e5adb - No-turn proposer ignore running commitWork task.
• 7e590e8 - No-turn proposer ignore running sealing block process.
• 24272d2 - core/types: faster RLP encoding of Header, StateAcccount, ReceiptForStorage (ethereum/go-ethereum#24420)
• 6d7eb6d - rlp/rlpgen: RLP encoder code generator (ethereum/go-ethereum#24251)

Docker Image

docker pull bitkubchainorg/node:2.2.0

v2.1.1

Changes

• (49d276e) graphql: avoid greedy allocation (ethereum/go-ethereum#27873)
• (52b7220) graphql: logs return error if from block > to (ethereum/go-ethereum#28412)
• (457b50b) graphql: return error if block from>to (ethereum/go-ethereum#28393)

Docker Image

docker pull bitkubchainorg/node:2.1.1

v2.1.0 - Chaophraya

Description

v2.1.0 is a hard fork release. The hard fork named Chaophraya hard fork.

Chaophraya hard fork is the big change on the consensus of Bitkub Chain. Bitkub Chain has transited the consensus from Proof-of-Stake-Authority (PoSA) to Proof-of-Stake (PoS) for more decentralize ecosystem. The PoS on Bitkub chain allows anyone to contribute the ecosystem as a validator by staking a native KUB, or share a risk with a validator node as a delegator.

The Chaophraya hard fork transition will be at block 14220246 on the Bitkub Chain Mainnet (August 17th 2023)

Noted, all the nodes on Bitkub chain must upgrade to this release before the Chaophraya hard fork.

Changes

• Add Chaophraya hard fork chain configuration and the checkpoint function.
• Upgrade Clique to support PoS
• Introduce new word called SPAN. SPAN is the period of group of selected validators has to perform block propagation.
• Add mechanism to distribute reward.
• Add mechanism to select next validator set.
• Add mechanism to propose new validator set to block signer list.
• Add mechanism to slash an unavailability node.
• No gas price for the system transactions
• Disable all propose function in Clique.
• Flag miner.sealerAddress and miner.etherbase are no longer support.
• No voting signer function.

Note: All of the changes will be backward compatible with Erawan hard fork on Bitkub chain until block number reach the chaophrayaBlock. All nodes must upgrade their Geth binary and re-initialize genesis file to prevent the BAD Block or other unpredictable incident.

v1.1.0 - Erawan

Description

v1.1.0-bkc is a hard fork release.

v1.1.0-bkc brings Erawan hard fork which changes the consensus mechanism from PoA to PoSA. The Erawan hard fork is scheduled to occur at block 5519559 on the Bitkub Chain Mainnet (Mar 31th, 2022).

Users of Bitkub chain must upgrade to this release before the Erawan hard-fork activates to remain in consensus.

Changes

• Add Erawan hard fork chain configuration and checkpoint function
• Propose the new flag miner.sealerAddress for sealing the block instead of etherbase.
• Use flag miner.etherbase as a beneficiary address
• Modify block header, using miner to record and track the beneficiary address
• Use Mix.Digest instead of Coinbase for voting signer
• Use Coinbase(inherited from miner.etherbase) for store the beneficiary address (the address that received the block reward)

Note: All of the changes will be backward compatible with official go-ethereum until block number reach the erawanBlock. Node runner both Validator node and RPC node must upgrade their geth binary and re-initialize genesis file (erawanBlock enabled) before erawanBlock to prevent the BAD Block