ZKsync, as reported by Odaily, has alerted users about a temporary compatibility problem arising during the protocol upgrade to version 26. The issue revolves around the Mailbox contract, which manages transactions between Layer 1 (L1) and Layer 2 (L2) and faces challenges due to the transition stages of bridging and L2 during the upgrade. It is anticipated that resolving this problem may span 1.5 to 2 weeks. To navigate this, users are encouraged to utilize ‘requestL2TransactionDirect’ and ‘requestL2TransactionTwoBridges’ on BridgeHub instead of relying on the Mailbox. ZKsync further advises users to consider migrating to BridgeHub to mitigate any risks associated with potential deprecation of the Mailbox contract in the future.
ZKsync’s Recommendations for Users
ZKsync’s guidance includes suggestions on how users can effectively manage the compatibility issue stemming from the protocol upgrade.
🔧 Why is the Mailbox Contract Experiencing Compatibility Issues?
During the protocol upgrade to version 26, the Mailbox contract, responsible for handling transactions between L1 and L2, has encountered challenges due to the evolving bridging and L2 transition phases. This has led to temporary compatibility issues that need to be addressed promptly.
🚀 What Steps Should Users Take?
To tackle this issue, ZKsync recommends utilizing ‘requestL2TransactionDirect’ and ‘requestL2TransactionTwoBridges’ on BridgeHub as viable alternatives to the Mailbox. By making this transition, users can navigate the compatibility concerns more effectively and ensure a seamless experience during the protocol upgrade.
💡 Why Consider Migrating to BridgeHub?
In light of potential future risks associated with the Mailbox contract, ZKsync advises users to consider migrating to BridgeHub. This proactive step can help users avoid any complications or disruptions that may arise from the deprecation of the Mailbox contract down the line.
To enhance search engine visibility, the following SEO-related tags are included:
#ZKsync protocol upgrade, #BridgeHub migration, #cryptocurrency compatibility issues