Skip to content
- EIP-7702 enables native support, enhancing account abstraction.
- The new RequestsHash field requires code adjustments.
- BNB Chain keeps blob target at 3, max at 6.
The Pascal hardfork on the testnet is scheduled on February 25, 2025, and the upgrade on the mainnet is intended to be completed around mid-March 2025. The upgrade is intended to catch up with the recent innovations on Ethereum and includes the addition of Ethereum Execution Layer EIPs included in the Pectra upgrade.
One of the notable inclusions is integration with the Ethereum’s EIP-7702 feature, a feature that upgrades smart contract wallet features and improves account abstraction on the BNB Chain.
While regular users on the BNB Chain are not going to see anything interrupted, developers and validators need to update their software in order to keep pace with the network upgrades. The upgrade is aimed at optimizing cryptographic processes, better cross-chain interactions, optimizing access to old data, and increasing efficiency in the entire network.
Smart Contract Wallets and Account Abstraction
A key feature in the Pascal hardfork is the inclusion of smart contract wallets with intrinsic support, enabled with the introduction of EIP-7702. The upgrade supports account abstraction in how users’ accounts are no longer in direct control under a private key.
This shift makes blockchain technology even more versatile and supports such added features such as multi-signature wallets, account restoration functions, spend limits, batching transactions, and session keys.
With this upgrade, BNB Chain is going in harmony with the developing landscape on Ethereum without sacrificing the efficiency on the network. Most existing smart contracts would not be affected and would continue working without a change, but extremely gas-sensitive projects would need to assess potential implications.
Implications for BNB Chain Users and Developers
No immediate step is necessary on the part of the typical BNB Chain user—whether in token holders, dApp users, or users of wallets like MetaMask and Trust Wallet. The token balances are not disturbed, and the necessary upgrades are taken care of by the wallet vendors. The upgrade is made in a way such that the users are not disturbed in a significant way.
However, validators and developers must prepare themselves for the update. The block header is modified in the Pascal hardfork with a new field added, RequestsHash, in accordance with BEP-466.
This field is aligned with Ethereum’s EIP-7685 and is going to be used in block header root hash calculations. All block header decoders and encoders are required to update their implementation in order not to suffer post-hard fork compatibility issues.
No Increase in Blob Throughput Unlike Ethereum
In contrast to Ethereum, which is expanding blob throughput as a component of its network upgrades, BNB Chain will stay in its present configuration. The blob target is still 3, with a maximum of 6, to provide a measured approach to scalability while incorporating Ethereum’s newest execution layer optimizations.
Conclusion
The Pascal hardfork represents a major milestone in BNB Chain development, nailing down compatibility with Ethereum and optimizing network efficiency. The introduction of smart contract wallets with native support and adjustment of block header structure is something that developers will have to adapt to, but regular users have nothing to fear.
Related Reading: Financial Services Committee Urges FDIC to Reform Crypto Banking Rules
