BNB Chain has scheduled its Pasteur hard fork for BNB Smart Chain at 2:30 a.m. UTC on Aug. 25, lining up a network upgrade centered on cross-chain transfer checks, validator permissions, and transaction handling. The update has been running on the test network since July 21.
According to the network, node operators need to install BSC software version v1.7.7 before the fork activates. Operators were also told to remove an older configuration setting, EnableBAL, because the new software will not start if that setting is still present.
Three proposals bundled into the upgrade
Pasteur combines three proposals: BEP-682, BEP-695, and BEP-675. The first two focus on security and validator controls, while the third changes how transactions are handled during block preparation.
BNB Chain said regular users and most application developers do not need to do anything for the upgrade. The main operational work falls on node operators and block builders, who are expected to complete the required software changes before activation.
Bridge checks will be tightened
Under BEP-682, BNB Smart Chain will change how it confirms transfers coming from another blockchain. Before assets are accepted, the chain will check whether a sufficient number of validators on the originating network approved the transfer.
The proposal is aimed at a specific weakness in the chain’s transfer validation process, although BNB Chain did not say the issue had been exploited to steal funds. The broader background is that cross-chain bridge attacks have led to more than $4 billion in losses since 2021, with stolen validator keys and weak transfer checks identified among the recurring problems in major incidents.
Validator key changes will carry stricter consequences
BEP-695 updates the rules for validators that rotate the digital keys used to perform network duties. Once a validator begins using a new key, the old key will lose its rights, rather than keeping residual access.
The proposal also keeps pending penalties attached to the validator after a key change. In addition, it extends the rule to votes submitted through signed messages, a step intended to stop blacklisted addresses from taking part in governance through outdated credentials.
Test results showed higher throughput, but live results remain unconfirmed
The third change, BEP-675, lets a block builder send a block that has already been processed. A validator can first confirm that the block meets network rules, approve it, and then carry out a deeper review afterward.
In tests on QANet, BNB Chain said transaction capacity increased to 2,324 transactions per second from 1,237 TPS. Block time remained at 450 milliseconds, while average use of each block’s available capacity rose from 46.35% to 84.15%. The network said those figures came from controlled testing and should not be treated as confirmed performance on the live chain.
The next confirmed step is the Aug. 25 activation on BNB Smart Chain. Ahead of that time, operators need to complete the software upgrade to v1.7.7 and remove the outdated EnableBAL setting so their nodes can start normally after Pasteur goes live.
Source: crypto.news