Deep Dive
Overview: This update streamlined the developer experience with improved plugins for popular frameworks and introduced new security features for the protocol. It makes building and deploying applications on ZKsync easier and more secure.
The release included updated Hardhat plugins (versions 1.2.0–1.6.0) that simplify testing and deployment, and Foundry updates that enabled major deployments like Aave. Key protocol advancements were the new Prover API, which lets third-party developers verify batch proofs, and the introduction of Trusted Execution Environment (TEE) proofs. TEE proofs run in "shadow mode" as an additional security layer alongside traditional ZK proofs.
What this means: This is bullish for ZKsync because it directly improves the experience for developers, which is crucial for ecosystem growth. Easier tooling lowers the barrier to building new apps, while multiple proof types make the network more robust and trustworthy for users.
(Source)
2. Security Council Protocol Upgrade (August 2025)
Overview: The ZKsync Security Council performed an urgent upgrade to fix a discovered protocol issue. The system's multi-layer security architecture prevented any breach during the process.
The upgrade was executed on 2 August 2025 after the issue was identified. The team confirmed the resolution and noted the system's "defense-in-depth" design kept it secure. A detailed post-mortem was promised to follow the initial announcement.
What this means: This is neutral to slightly bullish for ZKsync. It demonstrates the project has an active and capable security response team, which is essential for user safety. However, it also reminds users that complex protocols can have undiscovered issues.
(Source)
3. ZKsync Lite Deprecation Date Set (February 2026)
Overview: The team confirmed the final shutdown date for ZKsync Lite (version 1.0), the network's original rollup. This is a planned consolidation of resources onto the more advanced ZKsync Era and ZK Stack.
The deprecation is scheduled for 4 May 2026. On this date, block production will cease and the network state will freeze. Users are urged to withdraw assets for convenience, but all funds will remain claimable afterward. A read-only API will stay available for at least a year.
What this means: This is a strategic, bearish event for the Lite network but bullish for ZKsync's long-term vision. It streamlines development efforts onto modern, smart-contract-capable technology (Era), which should lead to better performance and more features for most users.
(Source)
Conclusion
ZKsync's development is bifurcated: actively refining developer tools and protocol security for its modern stack while methodically retiring its legacy proof-of-concept. This points to a project maturing its infrastructure and focusing resources on scalable, enterprise-ready solutions. How will the full transition away from Lite impact the network's user base and total value locked?