BNB Chain Sends Urgent Update Reminder Before April 28 Fork
BNB Chain has mandated that node operators execute a necessary software update ahead of the Osaka/Mendel hard fork, which is set to launch on the mainnet on April 28.
Summary
- BNB Chain node operators must upgrade to BSC v1.7.2 prior to the implementation of the Osaka/Mendel hard fork.
- The upgrade on April 28 follows its testnet activation and is designed to improve stability, gas limits, and finality.
- BNB Chain cautioned that outdated configurations and incorrect binary installations could result in nodes falling out of synchronization.
The network stressed that operators should transition to BSC v1.7.2 and eliminate legacy settings to ensure smooth node operations.
BNB Chain developers stated that node operators need to complete this update before the Osaka/Mendel hard fork is applied on the BSC mainnet, scheduled for April 28 at 2:30 a.m. UTC.
The notice accentuated the significance of properly replacing binaries and clearing old configuration fields to avert nodes from “losing sync” during the upgrade.
This announcement highlights the necessity for infrastructure readiness prior to the hard fork date, indicating that the update is essential for operators aiming to keep their nodes in sync with the chain.
The deadline aligns with BNB Chain’s transition from testnet preparations to a full mainnet rollout, which usually brings increased scrutiny on validator and node performance across the network.
The Mendel upgrade introduces BEP-652, which integrates EIP-7825 into BNB Chain, establishing a protocol-level gas limit of 16,777,216 gas for each transaction.
This adjustment ensures uniform transaction handling for all nodes exceeding the limit, with BNB Chain asserting that this method is more reliable than the previous soft cap model that allowed for variable interpretation by operators.
The extensive network upgrade consists of a total of nine BEPs. Furthermore, BNB Chain announced the integration of seven out of the 13 Ethereum proposals related to Fusaka, including six requiring a hard fork and one involving a client-side RPC adjustment.
The network chose not to adopt the remaining six proposals due to architectural differences. Additionally, it has introduced two BNB Chain-specific enhancements through BEP-657 and BEP-648.
Testnet rollout preceded mainnet launch
The Osaka/Mendel hard fork was activated on the BSC testnet by BNB Chain on March 24 at block 88,379,325. Developers observed that the test phase improved block construction, transaction processing, network stability, and execution accuracy.
BEP-657 specifies conditions under which blob transactions may be included based on the block number, while BEP-648 aims to reduce latency and expedite finality across the network.
The mainnet launch is contingent on operators completing the required update within the specified timeframe. The latest notice underscores BNB Chain’s goal of ensuring that nodes are properly prepared before the hard fork on April 28.
