Skip to content

v1.3.10
Compare
Choose a tag to compare
@github-actions github-actions released this 04 Mar 06:43
· 1567 commits to master since this release
v1.3.10
c8cc919

Notice

BSC will switch to PBSS and gradually stop support for hash based mode, if your nodes are still running with hash based mode, pls follow this doc to upgrade to PBSS: https://forum.bnbchain.org/t/faq-pbss-pebbledb/2260/6

Description

This release is going to enable the Feynman upgrade on BSC testnet. The upgrade is forecasted to occur on 11th March 2024 at 6:00 (UTC). The full node runners on testnet must switch their software version to the latest version by 11th March.

Feyman upgrade is the most important milestone of BNB Chain Fusion. The BNB Chain Fusion is a strategic shift to migrate the Beacon Chain’s functionalities to BNB Smart Chain (BSC) and retire Beacon Chain. This move aims to streamline the network, improve efficiency, reduce security risks, and align BNB Chain's architecture with the current technological demands and future growth. BEP333 propose to securely and smoothly transit the BNB Beacon Chain and BNB Smart Chain (BSC) from a dual-chain structure into a single chain structure and thus decommission the Beacon Chain.

Due to Feyman's upgrade, it will have a significant impact on the BNB ecosystem. We welcome the community to submit issues on GitHub or Discord. Kindly remind that BNB Chain has a bug bounty program if anyone find any security issues.

For BNB Beacon Chain Asset Holders

After BC Fusion, users will find it either impossible or extremely challenging to access assets on the BNB Beacon Chain. Here is a detailed guide designed to assist digital asset issuers and holders on the BNB Beacon Chain in transferring the value of their assets, like BEP2/BEP8 tokens, both before and after the Beacon Chain Fusion.

Here is an outline of all important milestones in the BNB Chain Fusion roadmap, set to facilitate a smooth transition for the BNB Chain community.

Brief Introduction of Feynman Upgrade

BEP-294, BEP-297 and BEP-299 will be deployed in the BSC Feynman hard fork.

  1. BEP-294 will take effect immediately. Validators created on BSC will receive triple voting power when staking an equal amount of BNB. This encourages the transfer of voting power from the Beacon Chain to BSC.

  2. The BEP-297 governance functionality will not be activated immediately after the hardfork. It will only be automatically enabled once more than 10 million BNB are migrated to BSC.

  3. The smart contract of BEP-299 is not available as the merkel root in the smart contract is still empty at this time. Only after the Beacon Chain comes to a complete halt, the Token Migration feature will be initiated by setting the Merkle root for balance dump through governance.

  4. Cross-chain re-delegation, which allows users to un-delegate their stakes from Beacon Chain and then delegate them on BSC in one Beacon Chain transaction, will be enabled after governance opening the related cross-chain channel.

Changelog

FEATURE

  • #2047 feat: add new fork block and precompile contract for BEP294 and BEP299
  • #2242 eth/gasprice: fix percentile validation in eth_feeHistory

Assets

Assets Sha256 Checksum
mainnet.zip aeeae3392bd51af57fb1e2eddeefff7e84d58a37f87513495348d82deee5824f
testnet.zip bcb79b8731c50ddaa3a5a2e3e92afa4f04b0c04c72b6b37b8a69ecd776304f15
geth_linux ad893fa61ee41dba05bb20447318ae1521944efba7402d3204a4712aac1e8ca4
geth_mac 73ab0acd0a75f899e649223daa3899555f83f2dde1d951986da272b61b2a59bf
geth_windows 4e162178f84b5a103e29ba1c21ce1e7e3bb7fb735f3a4225158d3244efa2bcc2
geth_linux_arm64 519ce8f6f5e4a31eac4ea71e102f04421407a918f5a103f4337d2e261e3953e7
Assets 8
Loading