Pasteur hardfork scheduled for BSC mainnet at 02:30 UTC on August 25

BNB Chain’s Binance Smart Chain is set to undergo its Pasteur hardfork on August 25, 2026, at 02:30 UTC, requiring every node operator on the network to upgrade to client version 1.7.7. The upgrade bundles cross-chain security fixes, staking governance hardening, and system contract changes designed to push the network closer to doubling its mainnet throughput.

What Pasteur actually changes

The hardfork is organized under a single umbrella proposal called BEP-673, which bundles two distinct improvements into one coordinated activation.

The first is BEP-682, which targets a specific vulnerability in CometBFT light client validation. Right now, it’s theoretically possible for duplicate validators to slip through the verification process used by cross-chain bridges. BEP-682 closes that gap by explicitly rejecting duplicate bridge validators.

The second component is BEP-695, focused on staking and governance security. The specifics center on tightening validator key rules so that the mechanisms governing who participates in consensus, and under what conditions, are harder to game.

Beyond the two BEPs, Pasteur also rolls out system contract upgrades aimed at expanding transaction capacity. BNB Chain has stated a goal of doubling mainnet throughput during the second half of 2026, and these contract-level changes are a direct step in that direction.

Testnet already cleared

BSC’s Chapel testnet activated a version of the Pasteur hardfork on July 21, 2026, running client version v1.7.6. That testnet run gave developers roughly five weeks of live data before the mainnet activation. The jump from v1.7.6 on testnet to v1.7.7 on mainnet suggests minor refinements were made after the testnet deployment.

Validators, exchanges, and decentralized applications have all received advance notice about the required upgrade.

Where Pasteur fits in BNB Chain’s roadmap

BNB Chain has been cycling through scientist-themed hardfork names, with Pasteur following a string of prior upgrades including Pascal, Mendel, and Fermi, each layering incremental improvements onto the network.

Staking participants should pay particular attention to the BEP-695 changes. Tighter validator key rules could affect how certain staking operations are configured, and validators who don’t adapt their setups could face penalties or exclusion from the active set.

Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.