BNB Chain Osaka/Mendel Hard Fork Set for April 28 With 9 Protocol Changes
The post BNB Chain Osaka/Mendel Hard Fork Set for April 28 With 9 Protocol Changes appeared on BitcoinEthereumNews.com.
Luisa Crawford
Apr 16, 2026 13:23
BNB Chain’s Osaka/Mendel upgrade introduces transaction gas caps, faster finality, and execution refinements. Node operators must update to BSC v1.7.2 before April 28.
BNB Chain will activate its Osaka/Mendel hard fork on April 28, 2026 at 02:30 UTC, introducing nine BEPs aimed at tightening execution efficiency following the network’s push to sub-second block times. Node operators who haven’t upgraded to BSC v1.7.2 risk losing sync with the mainnet. The upgrade arrives with BNB trading at $620.65, up 0.61% over 24 hours, and the network’s market cap sitting at $83.65 billion. What’s Actually Changing Osaka/Mendel isn’t chasing faster block times—the Fermi hard fork already pushed those down to 0.45 seconds. This upgrade focuses on what happens when you’re already running that fast: small inefficiencies compound quickly. The headline technical change is BEP-652, which establishes a hard cap of 16,777,216 gas per transaction. That’s not arbitrary. When blocks arrive every half-second, a single oversized transaction can cascade into processing delays. The cap makes block construction more predictable for validators and reduces the chance of gas spikes catching users off-guard. Six of the nine BEPs align with Ethereum EIPs, while two are BNB Chain-specific optimizations. The selective approach matters—BNB Chain isn’t blindly importing Ethereum changes but picking what actually improves performance in its faster environment. Developer and User Impact For builders, the changes include upper bounds on heavy operations like modular exponentiation, updated gas costs for secp256r1 cryptography, and a new CLZ opcode for counting leading zeros. That last one sounds obscure, but it gives developers more efficient low-level tools without changing how applications look to end users. A new JSON-RPC method (eth_config) also lands with this fork, improving visibility into node configuration. Debugging infrastructure issues should get easier.…
Filed under: News - @ April 17, 2026 5:26 am