BNB Chain has urged node operators to complete a mandatory software upgrade ahead of the Osaka/Mendel hard fork, which is set to go live on mainnet on April 28.
Summary
BNB Chain requires node operators to install BSC v1.7.2 before the upgrade.
The April 28 hard fork introduces improvements in stability, gas limits, and transaction finality.
Incorrect updates or outdated configurations could cause nodes to fall out of sync.
Mandatory update ahead of hard fork
Developers at BNB Chain said node operators must upgrade to BSC v1.7.2 before the Osaka/Mendel hard fork activates on mainnet at 2:30 a.m. UTC on April 28.
The network emphasized that operators need to properly replace binaries and remove outdated configuration settings. Failure to do so could result in nodes “losing sync” during the transition.
The update is essential for maintaining compatibility with the upgraded chain, making it mandatory for all operators who want their nodes to continue functioning normally.
Osaka/Mendel introduces protocol changes
The Mendel upgrade includes BEP-652, which integrates Ethereum’s EIP-7825 into BNB Chain by setting a protocol-level gas cap of 16,777,216 per transaction.
This ensures that all nodes uniformly reject transactions exceeding the limit, replacing earlier soft cap mechanisms that allowed inconsistent handling.
In total, the upgrade introduces nine BEPs. It also incorporates seven proposals from Ethereum’s Fusaka upgrade, including six requiring a hard fork and one client-side RPC change. Additional network-specific enhancements come through BEP-657 and BEP-648.
Testnet phase completed
The Osaka/Mendel upgrade was activated on the BSC testnet on March 24, where it improved block construction, transaction processing at scale, network stability, and execution accuracy.
BEP-657 introduces limits on blob transaction inclusion based on block number, while BEP-648 focuses on reducing latency and improving finality.
Focus shifts to mainnet readiness
With the mainnet launch approaching, BNB Chain is emphasizing infrastructure readiness. The network has made it clear that timely updates are critical to ensure smooth operation and avoid disruptions during the hard fork.
