Key Insights: Binance news reports that BNB Chain’s Pasteur hard fork activates Aug. 25 after QANet hit 2,324 TPS. BEP-675 cut critical-path processing from 125 ms to 15 ms in controlled test
As per the latest Binance news, BNB Chain will activate its mandatory Pasteur hard fork on Aug. 25. The move will bring changes to block processing, cross-chain verification and validator governance after controlled tests showed throughput reaching 2,324 transactions per second.
The upgrade requires every BSC mainnet node to run client version 1.7.7 before activation. While node operators must prepare for the transition, regular users and most application developers do not need to move funds or modify their software.
Pasteur combines three proposals, BEP-675, BEP-682, and BEP-695, that address different parts of BSC operations. The performance component produced the most apparent test result, although BNB Chain has not confirmed that the same throughput will appear under live mainnet conditions.
BEP-675 changes how builders and validators handle block execution during the time-sensitive production process. Under the new approach, builders can submit blocks they have already executed. Validators then check the proposed block against consensus rules before signing and broadcasting it.
Binance News Reports About Pasteur Going Live | Source: X Tests on QANet, an internal environment built to reflect BSC’s cross-region validator setup, reduced critical-path processing from 125 milliseconds to 15 milliseconds. At the same time, throughput increased from 1,237 TPS to 2,324 TPS. Average block gas usage rose from 46.35 million to 84.15 million against the existing 100 million limit.
However, the 450-millisecond block interval remained unchanged, as did finality lag. BNB Chain also said the figures came from controlled testing rather than mainnet activity.
Another part of the Pasteur hard fork, in addition to Binance news, BEP-682, changes how BSC verifies blocks involved in cross-chain transfers. The network will check validator signatures before accepting information from another chain, confirming that the required voting threshold approved the submitted block.
The proposal also closes a validator-set verification gap. Previously, the process did not verify that each validator appeared only once in a submitted set.
That meant a specially constructed set could repeat the same validator and count its voting power more than once. However, BEP-682 rejects duplicate validator entries, making the voting limit reflect the actual validator supermajority.
BEP-695 addresses consensus-key rotation and governance permissions. After Pasteur activates, an old consensus key will lose its administrative authority when a validator changes keys. Pending slash evictions will also transfer to the validator’s new key rather than disappearing during rotation.
The proposal on Binance news also prevents blacklisted addresses from using signature-based governance voting methods to circumvent restrictions on direct votes.
These changes operate through BSC staking, governance, and system contracts, meaning existing applications do not require migration.
Node operators must install BSC client version 1.7.7 before the hard fork. They must also remove [Eth] from config.toml, because leaving the setting in place will prevent the updated client from starting.
The release also recommends removing [TxPool], while several command-line flags have become obsolete or inactive. Pasteur has operated on BSC testnet since July 21.
After the Aug. 25 mainnet activation, the next measurable result will be whether the 2,324 TPS recorded on QANet appears under live network conditions.
The post Binance News: BNB Chain’s Pasteur Hard Fork Goes Live With 2,324 TPS Test Results appeared first on The Coin Republic.
