Hey everyone,
I’m Vlad from the Matter Labs team. Following the approval of ZIP-17, we’d like to share when the new execution delay will take effect on ZKsync Era.
What’s changing?
On Wednesday, October 7, 2026, at 9:00 AM ET (13:00 UTC / 15:00 CEST), the execution delay on ZKsync Era will be increased from 3 hours to 24 hours.
ZIP-17 passed the Token Assembly vote and has been executed, deploying an updated Validator Timelock that allows each EraVM ZK Chain to set its own execution delay. ZKsync Era will now adopt the 24-hour delay recommended in the proposal and in the Hardening EraVM blog post. A longer delay gives monitoring systems and security responders more time to identify and act on anomalous activity before a batch becomes final on Ethereum.
What this means for users:
- Withdrawals and other L2→L1 messages from ZKsync Era will take at least 24 hours to finalize on Ethereum, instead of at least 3 hours.
- The new delay applies to all batches not yet executed, including batches committed before the change. Withdrawals initiated shortly before October 7 may also be subject to the 24-hour delay.
- The execution delay is a minimum, not a guarantee. Actual L1 finality depends on network activity, proof generation, and batch aggregation, and may take longer.
- Transaction processing on ZKsync Era, including deposits from Ethereum, is not affected.
For exchanges, bridges, and integrators:
If your systems rely on L1 finality of ZKsync Era batches (for example, to process withdrawals or release liquidity), please update your expected confirmation times before October 7.
Other ZK Chains:
This change applies to ZKsync Era only. Under ZIP-17, each EraVM ZK Chain decides independently whether and when to increase its delay, and chains that take no action keep the current 3-hour default. If you are using another ZK Chain, please check with that chain directly for its current execution delay.