BNB Chain’s Pasteur hardfork is set for Aug. 25 with security and capacity changes

The network says the fork bundles three BEPs under BEP-673: BEP-682 rejects duplicate validators in light-block validation, BEP-695 tightens validator-key and governance handling, and BEP-675 introduces a builder-proposed block path that can be enabled after activation. The changes affect infrastructure more directly than ordinary wallet users.

Operators have a fixed upgrade deadline

BNB Chain says mainnet nodes must run v1.7.7 before the 02:30 UTC activation. Its release notes also warn operators to remove the [Eth] EnableBAL setting from config.toml before upgrading because leaving it in place can stop the node from starting. The signed v1.7.7 release identifies the Pasteur activation time and provides the mainnet binaries.

A node that misses a consensus upgrade can fall out of sync with the mainnet. That is an infrastructure risk for validators, RPC operators and service providers; BNB Chain says ordinary users do not need to move their BNB or change wallet settings for the fork.

Capacity claims are still testnet results

BNB Chain reports that a controlled QANet test increased transactions per second from 1,237 to 2,324 at the same 450-millisecond block interval and 100 million gas limit after the BEP-675 path was used. Those are internal testnet benchmarks under a specified workload, not a measured mainnet result or a promise of lower fees.

The upgrade's immediate verifiable event is the scheduled protocol change and the node-version deadline. Whether the capacity path produces comparable results on mainnet will depend on validator and builder adoption, workload, client behavior and the network's operating conditions after activation.