Deep Dive
1. Etherscan Support Ends (7 Jan 2026)
Overview: ZKsync Era will no longer be indexed by Etherscan, requiring users/developers to switch to ZKsync’s native explorer. This aligns with its evolution into a multi-chain network with features like cross-chain messaging and LLVM-based compilers.
What this means: This is neutral for ZKsync because it reduces reliance on third-party tools, offering deeper protocol-specific insights. However, developers must migrate APIs and tools, which could cause short-term friction. (Source)
2. ZKsync Lite Deprecation (2026)
Overview: The original ZK rollup (launched in 2020) will sunset in 2026, redirecting focus to ZKsync Era. Lite processes <200 daily transactions, with $50M in assets still bridged.
What this means: This is bullish for ZKsync because it consolidates resources into its advanced zkEVM ecosystem (ZKsync Era), which supports smart contracts and handles 22k+ daily operations. Users retain L1 withdrawal access. (Source)
3. Runtime Upgrade 1.3.1 (Nov 2025)
Overview: Introduced native EZKL verification (for AI workflows), allow-list controls for domain owners, and non-ZK Ultrahonk verifier support.
What this means: This is bullish for ZKsync because it expands use cases (e.g., verifiable AI) and gives developers granular control over proof submissions, enhancing flexibility for enterprise applications. (Source)
4. Atlas Upgrade (Oct 2025)
Overview: Activated native cross-chain interoperability, enabling ZK chains to share Ethereum’s liquidity. Achieved 15k TPS and 1-second finality.
What this means: This is bullish for ZKsync because it positions Ethereum as a liquidity hub for institutional capital (via Prividiums) and reduces latency for DeFi transactions. (Source)
5. Security Patch (Aug 2025)
Overview: Addressed a protocol vulnerability via a Security Council upgrade, leveraging ZKsync’s multi-layered security model.
What this means: This is neutral for ZKsync because it demonstrates proactive security measures but highlights ongoing risks in complex systems. A post-mortem was promised but not yet published. (Source)
Conclusion
ZKsync is prioritizing protocol independence (native explorer), scalability (Atlas), and enterprise-grade utility (runtime upgrades), while phasing out legacy systems. The shift from Lite to Era underscores its maturation into a modular ecosystem. Will native tooling adoption outpace short-term migration challenges?