BNB Chain has told node operators to complete a required software update before the Osaka/Mendel hard fork reaches mainnet on April 28.
The network said operators must install BSC v1.7.2 and remove outdated configuration fields to keep nodes running normally. Developers warned that incorrect binary replacement or old settings could cause nodes to lose sync during the upgrade. The hard fork is scheduled for April 28 at 02:30 UTC.
The Mendel upgrade introduces BEP-652, which implements EIP-7825’s protocol-level gas cap of 16,777,216 gas per transaction. With a protocol cap, all nodes will consistently reject transactions above the limit, replacing the earlier soft cap model that operators could treat differently.
Osaka/Mendel includes nine BEPs in total. BNB Chain adopted seven of 13 Ethereum proposals associated with Fusaka—six requiring a hard fork and one client-side RPC change—while declining six others due to architecture differences. The network also added two BNB Chain–specific updates via BEP-657 and BEP-648.
BNB Chain first activated the Osaka/Mendel hard fork on testnet on March 24 at block 88,379,325. Developers said the testnet phase enhanced block construction, large-scale transaction handling, network stability, and execution accuracy. BEP-657 limits when blob transactions can be included based on block number, and BEP-648 aims to reduce latency and speed up finality.
The mainnet launch now depends on operators completing the required update. The notice emphasizes infrastructure readiness and signals the update is mandatory for anyone who wants their node to stay aligned with the chain ahead of the April 28 hard fork.