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 should move to BSC v1.7.2 and remove outdated settings to keep nodes running normally.

BNB Chain developers said node operators must complete the update before the Osaka/Mendel hard fork goes live on BSC mainnet. The network scheduled the upgrade for April 28 at 2:30 a.m. UTC.

The notice said operators need to replace binaries correctly and clean up old configuration fields. The team said those steps are needed to stop nodes from “losing sync” during the upgrade.

The message places the focus on infrastructure readiness before the hard fork date. It also shows that the update is not optional for operators who want their nodes to stay aligned with the chain.

The deadline comes as BNB Chain moves from testnet preparation to a full mainnet rollout. That shift usually puts more attention on validator and node performance across the network.

Osaka and Mendel bring protocol changes

The Mendel upgrade adds BEP-652, which brings EIP-7825 into BNB Chain through a protocol-level gas cap for each transaction. The cap is set at 16,777,216 gas.

That change means all nodes will reject transactions above the limit in the same way. BNB Chain said this method is more reliable than the earlier soft cap model that operators could treat differently.

The broader network upgrade includes nine BEPs in total. BNB Chain also said it adopted seven of the 13 Ethereum proposals linked to Fusaka, including six that required a hard fork and one client-side RPC change.

The network did not adopt the other six proposals because of architecture differences. It also added two BNB Chain-specific updates through BEP-657 and BEP-648.

Testnet rollout came before mainnet launch

BNB Chain activated the Osaka/Mendel hard fork on the BSC testnet on March 24 at block 88,379,325. Developers said the test phase improved block construction, transaction handling at scale, network stability, and execution accuracy.

BEP-657 limits when blob transactions can be included based on block number. BEP-648 aims to reduce latency and speed up finality on the network.

The mainnet launch now depends on operators completing the required update on time. The latest alert shows BNB Chain wants nodes fully prepared before the April 28 hard fork begins.