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 tests.
- BSC node operators must install client v1.7.7 before Pasteur mainnet activation.
As per the latest Binance news, BNB Chain will roll out its mandatory Pasteur hard fork on Aug. 25. This update introduces modifications to block processing, exchange assets and data.">cross-chain verification, and validator governance following controlled tests that demonstrated transaction speeds reaching 2,324 transactions per second.
To prepare for this upgrade, every BSC mainnet node is required to run client version 1.7.7 prior to activation. While node operators need to make these adjustments, everyday users and the majority of application developers are not required to transfer funds or alter their software.
Pasteur integrates three distinct proposals—BEP-675, BEP-682, and BEP-695—targeting different facets of BSC operations. Although the performance enhancements yielded the most prominent test outcomes, BNB Chain has not guaranteed that identical speeds will translate directly to live mainnet environments.
BNB Chain Pasteur Tests Reach 2,324 TPS
BEP-675 alters how builders and stake participant that proposes and attests to blocks using bonded collateral.">validators manage block execution during the time-sensitive creation phase. Under this updated framework, builders can supply blocks that they have already executed. Validators then verify the proposed block against consensus rules prior to signing and broadcasting it.
Evaluations conducted on QANet, an internal environment designed to mimic BSC’s cross-region validator setup, decreased critical-path processing times from 125 milliseconds down to 15 milliseconds. Concurrently, volume a network can handle without fees or delays exploding.">throughput climbed from 1,237 TPS to 2,324 TPS. Average block gas usage expanded from 46.35 million to 84.15 million against the pre-existing 100 million limit.
Nevertheless, the 450-millisecond block interval and finality lag remained completely unaltered. BNB Chain also emphasized that these metrics stem from controlled trials rather than live mainnet operations.
Binance News Focus Turns to Cross-Chain Verification
In addition to general Binance news, BEP-682 represents another key facet of the Pasteur hard fork, modifying how BSC checks blocks involved in exchange assets and data.">cross-chain transactions. The network will examine validator signatures before accepting data from external chains, ensuring that the necessary voting threshold successfully approved the submitted block.
This proposal additionally rectifies a loophole in validator-set verification. Previously, the protocol failed to ensure that each validator appeared exclusively once within a given set.
Consequently, a specially crafted set could duplicate a specific validator and inflate its voting power multiple times. BEP-682 prevents this by rejecting duplicate validator entries, ensuring that voting thresholds accurately represent the genuine validator supermajority.
Pasteur Tightens Validator Key Controls
BEP-695 focuses on consensus-key rotation and permissions related to governance. Following the activation of Pasteur, an outdated consensus key will forfeit its administrative privileges whenever a validator transitions to a new key. Furthermore, any pending slash evictions will seamlessly migrate to the validator’s updated key rather than vanishing entirely during the rotation process.
The update highlighted in Binance news also blocks blacklisted addresses from utilizing signature-based governance voting methods as a workaround against restrictions placed on direct votes.
Because these updates function via BSC staking, governance, and system contracts, pre-existing applications do not necessitate any migration.
BNB Chain Nodes Must Upgrade Before Aug. 25
Node operators are required to install BSC client version 1.7.7 prior to the hard fork. They must also delete [Eth] from config.toml, as leaving this configuration in place will stop the newly updated client from launching successfully.
This software release likewise advises the removal of [TxPool], while several command-line flags have been deprecated or rendered inactive. Pasteur has already been running live on the BSC testnet since July 21.
Following the mainnet deployment on Aug. 25, the primary indicator to watch will be whether the 2,324 TPS benchmark logged on QANet materializes under live network conditions.
FAQ
- When does the Pasteur hard fork activate? It is scheduled to go live on August 25.
- What transaction speed did test results show? Controlled tests on QANet reached 2,324 transactions per second.
- What do node operators need to do? BSC node operators must install client version 1.7.7 and remove [Eth] from config.toml before activation.
- Do regular users need to migrate funds? No, regular users and most application developers do not need to move funds or modify software.
