Deep Dive
1. TEE Proofs & Prover API (September 2024)
Overview: This update added a second layer of security proofs generated inside a Trusted Execution Environment (TEE), making ZKsync the first rollup with multiple proof types. It also launched an API to let third-party developers verify proofs, starting the process of decentralizing the network's core function.
The new unstable_getTeeProofs RPC method allows access to these proofs, which initially ran in "shadow mode" alongside the existing zero-knowledge proofs. The Prover API provides endpoints for fetching batch data and verifying proofs, enabling external participation in the proof-generation process.
What this means: This is bullish for ZKsync because it makes the network significantly more secure and resilient by not relying on a single type of cryptographic proof. It also begins to distribute a critical function (proof generation) to the community, which is a major step toward true decentralization and long-term network health.
(Source)
Overview: The team released updated versions of core development plugins for Hardhat and Foundry, simplifying the process of testing, deploying, and upgrading smart contracts on ZKsync Era. This reduces friction for developers migrating projects from other Ethereum-compatible chains.
Key releases included hardhat-zksync v1.2.0, which consolidated several tools into one plugin, and foundry-zksync updates that enabled complex deployments like Aave. New migration guides were also published in the official documentation.
What this means: This is bullish for ZKsync because a better developer experience directly leads to more applications being built on the network. Easier migrations and more robust tools can attract development talent and increase the ecosystem's diversity and utility.
(Source)
3. Third-Party Integrations Live (September 2024)
Overview: This update marked the live integration of major infrastructure services, most notably Chainlink's Cross-Chain Interoperability Protocol (CCIP). It also included updated template contracts from thirdweb to support ZKsync Era and ZK Chains natively.
CCIP's activation enables secure cross-chain messaging and token transfers, connecting ZKsync to other blockchain ecosystems. The thirdweb update allows developers to quickly deploy common contract types using a familiar toolkit.
What this means: This is bullish for ZKsync because integrations with established projects like Chainlink provide immediate utility and connectivity for users and developers. It reduces the network's isolation and leverages existing, trusted infrastructure to accelerate adoption and complex application development.
(Source)
Conclusion
The September 2024 updates showcase ZKsync's commitment to strengthening its core protocol security with TEE proofs, decentralizing its infrastructure via the Prover API, and aggressively improving the developer onboarding experience. While these are not the most recent announcements (which have focused on roadmap and tokenomics), they represent significant, tangible advancements in the network's technical foundation. How will these deeper technical improvements support the ambitious institutional and RWA-focused goals outlined in ZKsync's 2026 roadmap?