Golden Finance reports that the Ethereum Layer 2 network ZKsync has posted a reminder on platform X that during the protocol upgrade v26, the Mailbox contract's backward compatibility is temporarily experiencing issues, which will affect L1→L2 transactions since relevant transactions are initially handled by the Mailbox contract. However, during the v26 upgrade, due to the bridge and L2 being in different transitional phases, backward compatibility is temporarily not functioning. Currently, resolving this issue may take 1.5-2 weeks, so users are advised to use "requestL2TransactionDirect requestL2TransactionTwoBridges" on BridgeHub instead of the Mailbox, and it is also recommended to migrate to BridgeHub to avoid future deprecation of the Mailbox contract.
The content is for reference only, not a solicitation or offer. No investment, tax, or legal advice provided. See Disclaimer for more risks disclosure.
ZKsync: The backward compatibility issue of the Mailbox contract may take 1.5-2 weeks to resolve.
Golden Finance reports that the Ethereum Layer 2 network ZKsync has posted a reminder on platform X that during the protocol upgrade v26, the Mailbox contract's backward compatibility is temporarily experiencing issues, which will affect L1→L2 transactions since relevant transactions are initially handled by the Mailbox contract. However, during the v26 upgrade, due to the bridge and L2 being in different transitional phases, backward compatibility is temporarily not functioning. Currently, resolving this issue may take 1.5-2 weeks, so users are advised to use "requestL2TransactionDirect requestL2TransactionTwoBridges" on BridgeHub instead of the Mailbox, and it is also recommended to migrate to BridgeHub to avoid future deprecation of the Mailbox contract.