The Binance-operated BNB Beacon Chain mainnet is set to add a new feature in its upcoming hard fork, which will allow the blockchain to “halt” the production of new blocks if certain conditions are met.

According to a July 12 statement from BNB Chain, the “ZhangHeng” upgrade is expected to take place at block height 328,088,888, which it expects will occur on July 19.

The hard fork will introduce Binance evolution proposal BEP-255, which seeks to implement “on-chain asset reconciliation.” Binance believes this could mitigate damage from potential cross-chain bridge exploits like the BNB Smart Chain exploit on Oct. 7, 2022. 

“Although some enhancements have been made to improve cross-chain security, such as BEP171, the security of assets on the BNB Beacon Chain itself should also be guaranteed, especially after the bridge exploitation,” according to the GitHub post concerning BEP-255. 

Binance explained that under the BEP-255, user balance changes will be tracked in each block and will be reconciled to identify any issues. “When there are reconciliation errors, the blockchain will panic and stop producing new blocks.”

Binance said the action would impact “downstream services such as bridges, deposits, and withdrawals on exchanges,” but the “drastic action” is necessary to protect the chain and its users. 

Bringing the blockchain back online will require a hard fork and addressing the reconciliation error. 

“For example, if exploitation exists, related accounts should be blacklisted or corrected. Once the blockchain is resumed, downstream services can be brought back up as well,” it explained.

Rogue key attacks and other upgrades

Other changes include a bug fix to prevent rogue key attacks — a security issue where a perpetrator produces a valid aggregate signature for a transaction as opposed to the true owner of the private keys.

“To fix the bug, all existing vote addresses will be cleared up when the height of hardfork reached,” the firm said, adding that validators will need to add vote addresses again.

The hard fork will also purport to make the chain capable of handling more complex business rules and logic.

Binance said the hard fork needs two-thirds of validators to switch their software version to v0.10.16 beforehand; otherwise, complications may arise.

Full nodes that fail to upgrade will not be able to execute further blocks after the hard fork block height, BNB Chain explained.

BNB Chain outlined a full set of instructions explaining how node operators can comply with the hard fork upgrade, but noted for BNB tokenholders that use Binance.com,  or other centralized exchanges or cold wallets, no action is currently required.

On June 19, BNB Chain launched opBNB — a new Ethereum Virtual Machine-compatible layer-2 scaling solution based on Optimism’s OP Stack.

Source