Other-News

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

By Sakamoto Nashi

1 / 15

Bridge Security and Validator Governance Get Tightened. BEP-682 is maybe the most quietly important piece of the whole upgrade.

2 / 15

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.

3 / 15

Node Operators Had No Choice But to Upgrade. For node operators, Pasteur wasn't optional. Anyone running the old software risked falling out of…

4 / 15

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…

5 / 15

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.

6 / 15

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…

7 / 15

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.

8 / 15

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…

9 / 15

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.

10 / 15

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

11 / 15

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

12 / 15

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.

13 / 15

BNB Chain was direct about the risk: run outdated software after the fork activation, and desynchronization follows.

14 / 15

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

15 / 15

The governance security piece is worth repeating, because it's easy to skim past in a list of BEP numbers.

The Currency Analytics

Want the full story?