BNB Chain will activate the Pasteur hard fork on BNB Smart Chain on August 25, tightening bridge and validator security while raising tested throughput. The upgrade leaves block intervals and gas limits unchanged, and node operators must upgrade before the cutover or risk falling out of sync.
BNB Chain will activate the Pasteur hard fork on BNB Smart Chain on August 25, adding bridge and validator security fixes plus higher tested throughput. The hard fork keeps the network's block interval and gas limits unchanged.
According to BNB Chain's Pasteur announcement, the hard fork activates at 2:30 a.m. UTC on August 25, following Chapel testnet work that began on July 21. The package sits under BEP-673 and combines three proposals in one coordinated mainnet cutover.
Pasteur hardens bridge checks and validator keys
BEP-682 tightens cross-chain bridge verification by rejecting duplicate validator signatures before transfer approvals count, using the same bridge design. Previously, repeated validator entries could inflate voting power and let fewer genuine signatures meet the threshold.
BEP-695 hardens staking and governance after key rotations. Retired consensus keys lose administrative authority, pending penalties stay attached to the validator through rotations, and blacklisted addresses cannot join signature-based governance votes.
Block processing path targets higher capacity
BEP-675 changes how builders and validators share work during block production. Builders can submit fully executed blocks for validator review instead of forcing every validator to re-run the same execution path immediately.
The design keeps the 450-millisecond block interval and existing gas limits. In controlled QANet testing, validator processing time fell from 125 milliseconds to 15 milliseconds, and throughput rose from 1,237 to 2,324 transactions per second under the same conditions. BNB Chain stressed that those figures come from controlled environments, not live mainnet traffic.
Node operators must upgrade before Aug. 25
Mainnet node operators must run BSC client v1.7.7 before activation or risk falling out of sync. Operators also need to remove the EnableBAL setting from configuration files, or the updated client will not start.
Several outdated command-line options are removed or disabled in the release. Most application developers and everyday users do not need a migration, though block builders adopting the new processing path must run full nodes rather than fast nodes.
Pasteur follows the earlier Fermi and Osaka/Mendel upgrades that cut block times.
Source: Live Bitcoin News
Trading involves risk.
Risk Disclaimer
