BNB Beacon Chain Introduces 'Panic' Feature for Halting Blockchain Operations

Around July 19, the "ZhangHeng" hard fork of BNB Beacon Chain mainnet is scheduled to occur. This hard fork will introduce additional improvements aimed at enhancing security.

The impending hard fork of the Binance-run BNB Beacon Chain mainnet is expected to provide a new feature that will allow the blockchain to "halt" the creation of new blocks if specific criteria are met.

The "ZhangHeng" upgrade is anticipated to occur at block height 328,088,888 on July 19, according to a statement made on July 12 by BNB Chain.

The security of assets on the BNB Beacon Chain itself should also be ensured, especially after the bridge exploitation, according to the Github post addressing BEP-255. "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," it states. 

According to Binance, the BEP will track user balance changes in each block and reconcile them to find any problems.

"The blockchain panics and stops creating new blocks when there are reconciliation errors."


Binance stated that although the "drastic action" is required to safeguard the chain and its users, it will have an impact on "downstream services such as bridges, deposits, and withdrawals on exchanges".

A hard fork and fixing the reconciliation mistake are both necessary for bringing the network back up. 

"For instance, connected accounts should be blocked or fixed if exploitation is present. Downstream services can be restarted as soon as the blockchain is running again, it said.

Attacks using a rogue key and other improvements

The "Rogue Key Attacks" security flaw, in which someone other than the legitimate owner of the private keys provides a valid aggregate signature for a transaction, has also been fixed.

When the hardfork height is reached, the company claimed, "all existing vote addresses will be cleared up to fix the bug," adding that validators would then have to add new vote addresses.

The hard fork will also claim to enable the chain to handle more intricate business logic and regulations.

Post a Comment