What Is ZKsync? A 2026 Guide to the Ethereum ZK Layer 2

ZKsync is a Layer 2 scaling network for Ethereum, developed by Matter Labs, a blockchain technology company founded in 2018. It processes transactions away from Ethereum mainnet, groups them into batches, and then posts a compact cryptographic proof to Ethereum showing that the batch was executed correctly. Because Ethereum verifies that proof, users get cheaper and faster transactions without handing trust to a separate set of validators for the correctness of state changes.

The project was originally branded zkSync, and you will still see that spelling in older articles and public reporting. Around 2024 the team moved to the styling ZKsync. Both refer to the same family of products.

The name covers several related things, which is why searches for it can be confusing:

• ZKsync Lite: the first network, launched in 2020, focused on token transfers and simple payments.
• ZKsync Era: the general-purpose smart-contract network that became the flagship and where most apps and users live.
• ZK Stack: an open-source framework for launching your own ZK-powered chains that connect to Ethereum and to each other.
• ZK token: the governance token tied to the ZKsync ecosystem, introduced in 2024.

In plain terms, ZKsync is both a place to use apps with lower fees and a toolkit for other teams to build their own chains. If you only want to swap, lend or mint, you interact with Era or another ZK Stack chain much like any other EVM-style network, using a compatible wallet and a small amount of gas. If you are a builder or an investor, the ZK Stack and governance layers matter more. The rest of this guide covers both angles.

ZKsync is a zero-knowledge rollup. A rollup executes transactions off-chain and then "rolls them up" into data that Ethereum stores or verifies. The zero-knowledge part is how the result is checked.

Here is the typical flow:

1. Users send transactions to the ZKsync network, where a sequencer orders them and gives quick confirmations.
2. The network executes them and updates its own state, including balances and contract storage.
3. A prover builds a validity proof that the whole batch followed the rules. Matter Labs developed its own proving system for this, and it has changed over time as the technology improved.
4. The batch and proof go to Ethereum. A verifier contract on Ethereum checks the proof. If it fails, the state change is not accepted.
5. Finality arrives once Ethereum has accepted the proof, and withdrawals can complete from that point.

This differs from optimistic rollups such as Arbitrum or Optimism. Those assume batches are valid unless someone challenges them during a dispute window. A validity-proof system proves correctness up front, so there is no fraud-challenge period built into withdrawals, although the proving and posting steps still take some time, and the practical delay depends on current network settings.

Proofs also compress. Instead of Ethereum re-running thousands of transactions, it verifies one proof, which spreads the cost over many users. Data availability matters here too. In rollup mode, the transaction data is published to Ethereum so anyone can reconstruct the state. Some ZK Stack chains choose validium mode, which keeps data elsewhere to cut cost, at the price of an extra trust assumption.

Matter Labs started the zkSync project in 2018 and launched the first live network, now called ZKsync Lite, in 2020. Lite was built around payments and simple swaps. It could not run arbitrary smart contracts, which limited what developers could deploy.

ZKsync Era was the answer to that. Often called zkSync 2.0 during development, it was designed to support general-purpose smart contracts written in languages familiar to Ethereum developers. It went through a public alpha phase and then reached a public mainnet launch in the first half of 2023. Era brought a zero-knowledge virtual machine, custom compilers for Solidity and Vyper, and native account abstraction.

The following years brought several changes:

• Rebranding: the styling changed from zkSync to ZKsync.
• New proving system: the team introduced upgraded provers to speed up proofs and cut costs.
• ZK token and governance: a token distribution in 2024 opened the door to community governance structures.
• ZK Stack and the "Elastic Network" vision: the focus moved from one chain to many connected chains sharing proofs and liquidity.
• Protocol upgrades: the team released numbered protocol versions that adjusted fees, compatibility and interoperability features.

The ecosystem also moved on from the earliest networks. Older products tend to be wound down as newer ones take over, so check the official ZKsync documentation to see the current status of ZKsync Lite and any legacy bridges before moving assets. If you hold assets on an older network, the safest step is to read the official migration or withdrawal guidance, not follow a link from a social post.

For users and developers, ZKsync Era offers a familiar experience with a few differences worth knowing.

EVM-style compatibility. Developers write contracts in Solidity or Vyper and compile them with ZKsync's own compilers. The network runs its own virtual machine rather than being a byte-for-byte copy of the Ethereum Virtual Machine. Most standard contracts and tools work with little change, but some low-level behaviour differs, so teams should read the documentation and test on a testnet before deploying.

Native account abstraction. On ZKsync, every account can behave like a smart contract wallet. That enables features that are hard on plain Ethereum accounts:

• Social recovery or multi-signature logic.
• Session keys that let an app act within set limits.
• Custom signature schemes, including passkeys in some wallets.
• Batching several actions into one transaction.

Paymasters. A paymaster is a contract that can pay gas for a user or accept another token as payment. Apps can use it to offer gasless onboarding or to let users pay fees in a stablecoin. Whether a given app uses this depends on its own design.

Low fees. Fees are generally lower than on Ethereum mainnet because costs are shared across a batch. The exact figure moves with Ethereum gas prices and network demand, so check a live gas tracker or the block explorer instead of relying on a fixed number.

For everyday use, you can use the same kinds of apps you would find elsewhere: decentralised exchanges, lending markets, NFT marketplaces and bridges. Which specific apps are live and liquid changes over time, so check current activity before depositing.

The ZK Stack is an open-source framework for building customised ZK-powered blockchains. Instead of every project deploying a contract on one shared network, a team can launch its own chain with its own rules, fee token, and sequencer set, while still connecting to Ethereum for settlement and to other ZKsync chains for messaging.

The pitch has three parts:

• Customisation: chains can pick rollup or validium mode, choose a fee token, and add permissions or compliance features if a business needs them.
• Shared interoperability: chains built on the stack are meant to move assets and messages between each other without the slow, trust-heavy paths of typical bridges.
• Shared proving and security model: chains use the same proof system and settle to Ethereum, which is intended to keep a single standard for verification.

The collective of these chains is often called the Elastic Network. Several projects, including consumer-focused chains and institutional pilots, have launched or announced chains on the stack. Because that list changes, check the official ZKsync ecosystem pages for what is live now.

For users, the practical point is that "ZKsync" may mean different chains with different assumptions. One chain may post all data to Ethereum, while another may rely on an external data-availability layer. One may be run by a single operator while another is more decentralised. Before you bridge funds to any ZK Stack chain, check three things: who operates the sequencer, where the data goes, and which keys can upgrade the contracts. Those answers matter more than the ZKsync branding.

The ZK token is the governance token of the ZKsync ecosystem. It launched in June 2024 through a large community distribution to eligible wallets, often called the ZKsync airdrop. Reported total supply is 21 billion tokens, though you should confirm current supply and unlock schedules on official sources and live data trackers, since vesting changes circulating numbers over time.

The token's role is mainly about governance. The structure includes a token assembly, where holders vote on proposals, and other bodies intended to review and guide decisions. The aim was to move control of the protocol gradually from the founding company to the community. How much real decentralisation exists in practice is a fair question for any young governance system, so read current proposals and voting records to judge it yourself.

A few points to keep clear:

• The ZK token is not required for gas on ZKsync Era. Gas on the main network has been paid in ETH.
• Governance rights are not the same as ownership or profit rights. Holding the token does not entitle you to income from the network.
• Price, market cap, circulating supply and unlock dates change constantly. Use a reputable data tracker and the official documentation, and treat any figure in an article as dated.
• Airdrop-related scams are common. Fake claim pages and fake support accounts target holders and farmers. The ZK token launch was a past event, so no new claim should come from a random message or link.

If you want to take part in governance, use only the official governance interfaces and verify the contract addresses against the official documentation before signing anything.

Using ZKsync follows a familiar pattern for anyone who has used another Ethereum Layer 2.

1. Set up a wallet. Use an Ethereum-compatible wallet and add the ZKsync network from the wallet's built-in list or from the official documentation. Check the chain ID against the official source.
2. Get ETH onto the network. You have three main routes:

• The official bridge, which moves assets from Ethereum mainnet to ZKsync using the canonical path.
• A third-party bridge or intent-based swap tool such as Across or Hyperlane, which may be faster or cheaper from other chains. Confirm that the tool currently supports ZKsync and the specific chain.
• A centralised exchange withdrawal, if your exchange lists the ZKsync network as a withdrawal option. Exchanges such as OKX, Bitget or Gate may or may not support it at any time, so check the withdrawal network list in your account.

3. Start small. Send a test amount first and confirm it arrives on the right network.
4. Use apps through their official sites. Bookmark them instead of searching each time.
5. Review approvals. After using an app, revoke token approvals you no longer need.

For stablecoins, check which version of the token exists on ZKsync. Bridged tokens and natively issued tokens can have different names and risks. Tether's USDT0 system and Chainlink CCIP are examples of cross-chain standards that aim to unify token liquidity, but support depends on the chain and token, so confirm before relying on them.

If you are exploring crypto gambling products that accept Layer 2 deposits, you must be 18 or older, and you should check the laws where you live. Do not use any tool to bypass age checks, KYC or regional restrictions.

ZKsync is one of several major Ethereum Layer 2 networks. The table below compares general design choices. Details change with upgrades, so confirm them in each project's current documentation.

Feature	ZKsync Era	Arbitrum One	Linea
Proof type	Validity (zero-knowledge) proofs	Fraud proofs (optimistic)	Validity (zero-knowledge) proofs
Developer approach	Own VM with custom compilers, EVM-style tooling	Close to EVM equivalence	zkEVM aiming for EVM equivalence
Account model	Native account abstraction	Standard accounts, with smart wallets on top	Standard accounts, with smart wallets on top
Multi-chain framework	ZK Stack and Elastic Network	Orbit chains	Focused mainly on its own chain
Withdrawals to Ethereum	Tied to proof posting and finality	Traditionally a dispute window, unless a fast bridge is used	Tied to proof posting and finality

What the table means in practice:

• If you care most about liquidity and the number of apps, check live data. Larger ecosystems are not always the ones with the best design.
• If you want smart-wallet features such as paymasters and session keys, ZKsync's native account abstraction is a strong draw.
• If you are a builder who wants your own chain, the ZK Stack and Arbitrum Orbit are direct alternatives.
• If you need to move funds between L2s, each has its own canonical route, such as Arbitrum Bridge for Arbitrum or Linea Bridge for Linea, plus third-party options.

No network is best for everything. Pick based on the apps you want to use, the fees you see on the day, and the security model you are comfortable with.

A validity-proof rollup has strong security properties, but there are still ways to lose money. Understanding where the risks sit helps you avoid the common ones.

Protocol-level risks

• Upgrade keys and governance: many Layer 2s can be upgraded by a small set of keys or a council. Read who controls upgrades and whether there is a delay before changes take effect.
• Sequencer centralisation: a single operator ordering transactions can censor or go offline. Rollups usually offer an escape route to Ethereum, but it may be slow or complex.
• Prover and contract bugs: proof systems and verifier contracts are complex. Audits reduce risk but do not remove it.
• Validium trade-offs: if a chain keeps data off Ethereum, users depend on the data provider for recovery.

User-level risks

• Fake bridges and phishing: scammers copy bridge and claim pages. Always navigate from a bookmark you trust.
• Unlimited token approvals: revoke ones you no longer need.
• Wrong-network deposits: sending tokens to the wrong chain or address can be unrecoverable.
• Wrapped and bridged token risk: a token on ZKsync that was bridged from elsewhere depends on the bridge's security.
• DeFi risk: lending, staking and yield apps carry smart-contract, oracle and liquidation risk of their own.

A defensive checklist

1. Test with a small amount first.
2. Verify contract addresses from the project's official documentation.
3. Use a hardware wallet for significant funds.
4. Never share your seed phrase, and ignore unsolicited support messages.
5. Keep only what you need on any single chain.

Figures for fees, total value locked, token supply and active users change quickly, so this guide does not state them. Here is where to look and what to check.

• Block explorer: the official ZKsync Era block explorer shows transactions, blocks and contracts. Use it to confirm a transfer arrived, inspect a contract, or check a token's address and holders before you trade.
• Official documentation: this is the source for network details, chain IDs, protocol upgrade notes, bridge instructions and the status of older networks such as ZKsync Lite.
• Live analytics dashboards: reputable Layer 2 data trackers publish TVL, transaction counts, fees and risk assessments. Compare more than one source, and note how each defines its numbers.
• Governance forums and voting pages: read proposals and results to see how the community is actually making decisions.
• Bridge and exchange support pages: before you move funds, confirm that your bridge or exchange currently lists the exact network and token you want.

When reading any ZKsync article, including older guides from 2023 to 2025, check the publication date. The network has changed since then, through rebranding, new proof systems, token launches and protocol versions, so details about fees, tokens and features may be out of date.

If you want exposure beyond using the chain, such as staking, check which assets are supported on ZKsync before assuming a product exists there. Staking and liquid staking protocols like Lido and Rocket Pool operate mainly on Ethereum mainnet, and the availability of their tokens on a given Layer 2 varies. Infrastructure providers such as Ankr offer RPC services that developers can use to connect to ZKsync chains.