Historical source: Matter Labs’ official zkSync repository
| Protocol documentation | Documentation |
|---|---|
| Directories | Ethereum Whitepapers & Research |
Scope and Evolution
This page separates original zkSync (zkSync Lite, v1) from the later zkSync Era and evolving ZKsync Stack. Matter Labs’ repository describes the early rollup design for ETH and ERC-20 transfers; this is a historical overview, not a single specification for the entire current ZKsync network.
zkSync Lite Design
In the zkSync Lite design, users transact on layer 2, an operator batches transactions, and validity proofs plus public data update Ethereum contracts. The rollup model is intended to let users recover assets from on-chain data without relying on an operator to keep cooperating. Those guarantees depend on the contracts, data availability, upgrade mechanisms, and the actual system in use.
ZKsync Status and Architecture Changes
ZKsync Era is a distinct system whose architecture has since changed. The official upgrade history records that the October 2025 Atlas upgrade introduced ZKsync OS and Airbender for the ZK Stack. On September 4, 2026, ZKsync announced a planned EraVM transition within the next six months; detailed dates and steps were still to be announced on official channels.
Governance and Limits
Upgrade controls and administrative roles are material trust assumptions, not details to omit. This page does not repeat older incident claims without a verifiable primary source; readers should check the linked security documentation and transition announcement for current status.
Related Terms
See Also
Sources
- Matter Labs’ official zkSync repository — Source documentation for the historical zkSync Lite/v1 design and early rollup goals.
- Official docs: ZKsync Era — Describes Era as a ZK rollup and its currently documented architecture and components.
- Official docs: Upgrades and Migrations — Records the October 2025 Atlas upgrade and introduction of ZKsync OS and Airbender.
- Official ZKsync announcement, September 4, 2026 — Announces the planned EraVM transition and says detailed steps and dates will follow.