Today, in coordination with the ZK Security Council, we released a new protocol version and proposed it to all ZKsync chains. The update corrects an overly strict condition in one of the ZK circuits.
No proofs or user funds were affected, and the condition was not exploitable. A
Joined November 2021
- The governance proposal for the v31 upgrade is now live! Below is a breakdown of what's included in v31.
- If it hasn’t been attacked, it hasn’t been tested. BattleChain testnet is where that happens. Built on @zksync stack, live now → battlechain.comAs of today, BattleChain testnet is LIVE. The pre-mainnet, post-testnet blockchain, where whitehats legally attack your smart contracts before they reach production. Deploy. Get attacked. Ship stronger. Here's why we built it, what it is, and how you can get involved 🧵
- 🚨 ZKsync is deprecating legacy Mailbox functions in favor of the new multichain (Elastic Network) interfaces. If you’re currently using requestL2Transaction or finalizeEthWithdrawal, migrate to Bridgehub and L1Nullifier within the next 6 months. Details →
- Today, in coordination with the ZK Security Council, we deployed an emergency upgrade to ZK chains. This update tightens cryptographic security and reduces the risk of misuse by a malicious operator. No user action is required, and ZKsync Era remains fully operational.



