ZKsync Developers (∎, ∆)

Developer and status updates for the @ZKsync Elastic Network.

[ZKsync Developers (∎, ∆) @zkSyncDevs]

Exchanges, bridges, and integrators relying on Era L1 finality: please update expected confirmation times before Oct 7.

Other ZK chains set their own delay independently.

Details 👇 https://t.co/3hzAhalQ5V

[ZKsync Developers (∎, ∆) @zkSyncDevs]

ZKsync Era's execution delay is increasing from 3h to 24h, following the approval of ZIP-17.

📅 Wednesday, Oct 7, 13:00 UTC (9:00 AM ET / 15:00 CEST)

A longer delay gives security responders more time to act before a batch is final on Ethereum 🧵

[ZKsync Developers (∎, ∆) @zkSyncDevs]

What this means:

▪️ Withdrawals from Era will take at least 24h to finalize on L1
▪️ Applies to all batches not yet executed, including those committed before Oct 7
▪️ Deposits and L2 transactions are unaffected
▪️ No user action required

[ZKsync Developers (∎, ∆) @zkSyncDevs]

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 technical summary will be shared once the update has fully propagated across all chains.

No user action is required, and ZKsync chains remain fully operational.

[ZKsync Developers (∎, ∆) @zkSyncDevs]

Read more details in the governance proposal and in the ZKsync developer discussions:
https://t.co/7YAvlVQDNV

[ZKsync Developers (∎, ∆) @zkSyncDevs]

The governance proposal for the v31 upgrade is now live!
Below is a breakdown of what's included in v31.

https://t.co/iaLiBHWOKy

[ZKsync Developers (∎, ∆) @zkSyncDevs]

🚨 Deposits and withdrawals will be temporarily paused during the upgrade.

When the ecosystem upgrade gets executed for all chains on mainnet, the deposits and withdrawals will temporarily stop working for a few hours.

[ZKsync Developers (∎, ∆) @zkSyncDevs]

@cyfrin 🎯

[ZKsync Developers (∎, ∆) @zkSyncDevs]

If it hasn’t been attacked, it hasn’t been tested.

BattleChain testnet is where that happens.

Built on @ZKsync stack, live now → https://t.co/4RUPv0xPhW

[Cyfrin Audits @cyfrin]

As 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 Developers (∎, ∆) @zkSyncDevs]

@blockscout 🙌👏

[ZKsync Developers (∎, ∆) @zkSyncDevs]

🚨 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 → https://t.co/9XauTuv6Rg

[ZKsync Developers (∎, ∆) @zkSyncDevs]

Huge thanks to our security team, researchers, and security council members for helping keep the ZKsync protocol secure.

[ZKsync Developers (∎, ∆) @zkSyncDevs]

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.

[ZKsync @zksync]

Airbender just took the #1 spot on @eth_proofs.

Leading on both proving time and cost per proof, across single-GPU and multi-GPU categories.