The BNB Beacon Chain testnet is expected to have a scheduled hard fork upgrade at block height 30,516,226. Based on the current block generation speed, the hard fork is forecasted to occur on 16 Sep. at 7:30 (UTC). The full node runners on testnet must switch their software version to v0.10.2 by September 16th.
1. Background Story
1.1 Who is Josiah Willard Gibbs?
This upgrade is named after Josiah Willard Gibbs in honor of his significant theoretical contributions to physics, chemistry, and mathematics. His work on the applications of thermodynamics was instrumental in transforming physical chemistry into a rigorous inductive science. Together with James Clerk Maxwell and Ludwig Boltzmann, he created statistical mechanics.
1.2 What is a Hardfork upgrade?
A Hardfork is an upgrade that is incompatible with the previous release because some breaking changes are introduced in the latest release. A hardfork in BNB Beacon Chain requires 2⁄3 of validators to upgrade to make blocks successfully. If the existing full nodes in the network do not upgrade, they will not receive and execute further blocks after the hardfork block height.
1.3 What happens during a network upgrade?
New rules and logic changes will occur for this upgrade at block height of 30,516,226. After the upgrade kicks in, the blockchain can handle a series of new business rules and logic.
2. How does this upgrade affect me?
2.1 As a BNB holder, what do I have to do?
If you are using any exchanges which support BNB (such as Binance.com, BitMax, or Gate.io), one of the wallets, or a hardware wallet (such as Ledger, Cool Wallet), there’s no action required on your side unless your exchange or wallet service notifies you.
2.2 As a full node operator, what do I have to do?
This is a hardfork release, and you need to switch to v0.10.2. Upgrade instructions are as below (you should do all the below before the hardfork block height):
- If your node is already synced with the network, please download the new v0.10.2 binary and replace the previous version, and download the new config file app.toml to replace the previous version.
- Increase the open file limit to 65535.
- Stop the bnbchaind process and restart it with v0.1cccccckrtuvntdgtudnbkcbngbducfbbklgibvrchn0.2.
ulimit -n 65535
bnbchaind start –home <home-path>
2.4 What will happen if I forget to upgrade my full node in time?
If you fail to upgrade your software on time, your node will not sync with the upgraded BNB Beacon Chain peer/validator nodes. You will not be able to connect or send transactions.
How to recover?
You can find detailed info at doc-site.
- Download the tool state-recover from node-binary repo for fixing the upgrade issue
- Backup your home directory
Since the height of the upgrade is set to be 30,516,226, you can run the following command to recover the state to just one block before the upgrade, which is 30,516,225:
- Restart with the version v0.9.0 of bnbchaind
3. Upcoming Changes
3.1 What will change with the blockchain feature?
BEP153 introduces a native staking protocol onto BNB Smart Chain. With this BEP, individual or institution delegators can stake BNB to specified validators and get staking rewards on the BSC side directly.
In order to coordinate with BEP-153 which will introduce native staking module onto BSC, there are some changes to be made, which mainly includes a new app to handle requests of BEP153 and necessary modifications to delegation’s data structs.
3.2 What will be different for users?
There will be no difference for users of BC.
Thanks for your cooperation, and let’s make BNB Beacon Chain a modern and secure infrastructure for the BNB ecosystem.
Follow us to stay updated on everything BNB Chain!
Website | Twitter | Telegram | Youtube | Discord | Reddit | Build N’ Build Forum