BNB Chain’s Pasteur Hard Fork Achieves Seamless 2,324 TPS on Mainnet Launch

BNB Chain flipped the switch. At 02:30 UTC on August 25, the Pasteur hard fork went live on the BSC mainnet, and the network didn’t skip a beat — blocks kept coming at the usual 450-millisecond interval with zero disruptions reported.

The upgrade bundles three separate improvement proposals — BEP-682, BEP-695, and BEP-675 — under the umbrella plan known as BEP-673. None of these changes appeared overnight. Developers had been running the whole package through BSC’s Chapel testnet since July 21, giving the ecosystem roughly five weeks to find problems before the mainnet push. The fact that the activation went cleanly probably owes something to that prep window. Still, the real test isn’t a testnet. It’s the live network, with real validators, real builders, and real money moving across bridges every second.

Bridge Security and Validator Governance Get Tightened

BEP-682 is maybe the most quietly important piece of the whole upgrade. It changes how light blocks get verified, specifically by rejecting duplicate validator entries from the count. Sounds technical. But the practical point is pretty clear: if the same validator could be counted more than once toward the supermajority needed for bridge approvals, bad actors had a potential path to misrepresent how much support a cross-chain transaction actually had. BEP-682 closes that gap. Bridge security across major blockchain networks has been a persistent weak spot industry-wide, so tightening the light block verification process matters more than the dry BEP language makes it sound.

BEP-695 handles a different kind of problem — validator key rotation. When a validator swaps its operator key, the old key should lose all management rights immediately. Before BEP-695, that wasn’t guaranteed, which meant a validator could theoretically rotate keys to dodge penalties. The upgrade kills that loophole. On top of that, BEP-695 blocks restricted addresses from sneaking governance influence through offchain signatures. The upgrade checks the original signer of any delegated vote, so blacklisted accounts can’t route around governance barriers through proxies or delegation tricks. That’s a meaningful integrity fix for anyone who cares about whether BNB Chain governance votes actually mean what they say.

BEP-675 Pushes Throughput — But Only If Builders Show Up

BEP-675 is the capacity play, and it’s the one with the most interesting asterisk attached. The proposal creates an optional new route for specialist block builders to submit pre-executed blocks directly. Validators can then verify those blocks and broadcast them, cutting out redundant execution steps. In BNB Chain’s internal test environment, QANet, throughput jumped from 1,237 transactions per second to 2,324 transactions per second. Gas consumption rose sharply during those tests too, though the block gas limit itself didn’t change.

And that’s the catch. Pasteur doesn’t touch the block gas limit or the block interval. The 450-millisecond rhythm stays exactly as it was. The capacity gains are real in testing, but they don’t materialize automatically on mainnet. They depend entirely on how many builders actually adopt the BEP-675 process. If builders don’t integrate the new submission route, the throughput numbers from QANet stay theoretical. BNB Chain basically built a faster lane on the highway — but drivers have to choose to use it.

See also: South Koreas 3,500 Corporate Crypto Accounts Propel Institutional Shift in Digital Finance

The network said it plans to watch key metrics closely after the fork: block utilization, validator performance, and actual transaction throughput under live conditions. Those numbers will tell the real story.

Node Operators Had No Choice But to Upgrade

For node operators, Pasteur wasn’t optional. Anyone running the old software risked falling out of sync with mainnet entirely. The required client version was 1.7.7, and operators also had to strip out deprecated configurations — specifically the EnableBAL field — that would’ve caused compatibility problems with the new client. It’s the kind of housekeeping that sounds minor but can wreck a node’s ability to follow the chain if it gets skipped.

BNB Chain was direct about the risk: run outdated software after the fork activation, and desynchronization follows. That’s a hard enough consequence that most serious operators probably updated well before the August 25 deadline.

See also: Pakistans SECP Demands Crypto Firms Register by September 5 or Face Shutdown

The governance security piece is worth repeating, because it’s easy to skim past in a list of BEP numbers. Restricted addresses can’t influence governance now — not through direct votes, not through offchain signatures, not through delegated proxies. The upgrade checks who originally signed. That’s a meaningful shift in how governance integrity gets enforced on the network.

BNB Chain’s internal tests put peak throughput at 2,324 transactions per second under the new builder submission model.

Hub: BNB price, news, and analysis