DeepChain深链
Layer 2 explainer 04 / 07  |  zksync  |  zk  |  4 min read
ZK

zkSync: a mathematical proof instead of a seven-day wait

A ZK Rollup developed by Matter Labs. Every batch of transactions comes with a zero-knowledge proof that Ethereum verifies, so withdrawals do not wait for a challenge period. Big technical ambitions, but very little money on the chain so far.

Layer 2 · zkSyncData as of 16 Oct 2026, 01:45 UK timeWebsite zksync.io ↗
Block time
4.45 s
L2BEAT stage
Stage 0

How a ZK Rollup differs from the previous three

Base, Arbitrum and Optimism are all Optimistic Rollups: the books are assumed correct and there are about 7 days for anyone to find an error.

A ZK Rollup works the other way round: every submission must come with a mathematical proof that “this batch of transactions really was executed by the rules, and this is the result”. A contract on Ethereum checks the proof in milliseconds, without trusting anyone and without waiting for someone to find a fault.

An analogy: Optimistic is “ship first, with seven days to return”; ZK is “produce a notarised report before shipping, and it takes effect once checked”. The cost is that the “notarised report” is hard to compute, needs a lot of specialised computing power, and the technology is far more complex.

Where it came from

  • 2020: Matter Labs launched zkSync Lite, an early version mainly for transfers.
  • March 2023: zkSync Era mainnet opened to everyone, one of the first ZK Rollups able to run general smart contracts (a zkEVM).
  • June 2024: the ZK token was issued and airdropped.
  • ZK Stack: like the OP Stack, Matter Labs open-sourced a toolkit so others can build chains with the same technology, hoping they will form an interoperable network.

One feature of zkSync is native account abstraction: every account can be a smart contract wallet, supporting fees paid in other tokens, social recovery, batched transactions and more, without deploying an extra set of contracts as on Ethereum.

How a transaction travels

how it worksHow a transaction gets on-chain
  1. 01Signed and sent

    The transaction goes to zkSync's sequencer. Fees are paid in ETH, or can be sponsored by the app.

    Instant
  2. 02Sequencer produces a block

    The sequencer puts the transaction into a Layer 2 block.

    Measured about 4.45 s per block
  3. 03Proof generated

    Dedicated "provers" compute a zero-knowledge proof for a batch of blocks; this is the most compute-heavy step.

    Tens of minutes to hours
  4. 04Verified on Ethereum

    The proof and state diff are submitted to Ethereum and take effect once the contract verifies them.

  5. 05Finalised

    No challenge period is needed after verification; withdrawals are available after the execution delay set by the protocol.

In theory ZK Rollup withdrawals are fast; in practice teams usually add an execution delay as a safety buffer. Check the official documentation for the current value.

L2BEAT’s assessment

ZK proofs settle whether the books are right, but not who is in control. L2BEAT currently rates zkSync Era only Stage 0: if the sequencer halts or censors, users can only put transactions into a queue on Ethereum, not force them through; and contract upgrades leave users no time to exit.

l2beat riskData as of 16 Oct 2026, 01:45 UK time · source L2BEAT
Security stage: Stage 0 (ZK Rollup)
  1. Stage 0

    Still on "training wheels": proofs may not be live, or the operator can change the rules alone

  2. Stage 1

    Proofs are live, but a security council can still override or upgrade in an emergency

  3. Stage 2

    Fully governed by code and proofs; nobody can change outcomes unilaterally

If the sequencer failsIf the official sequencer goes down or censors you, can you still force your transaction in?
Enqueue via L1
Fair
State validationWho guarantees that the state the Layer 2 posts to Ethereum is correct
Validity proofs (ST, SN)
Good
Data availabilityIs all transaction data published on Ethereum, so the chain can be rebuilt if something goes wrong
Onchain (SD)
Good
Exit windowDo users have time to withdraw before the contracts are upgraded
None (can be upgraded instantly)
Poor
If the proposer failsIf the role that posts state to Ethereum stops, can users still withdraw
Replace proposer
Fair

What is on-chain today

live dataData as of 16 Oct 2026, 01:45 UK time
Security stage (L2BEAT)Stage 0ZK Rollup (validity proofs)
Value secured (TVS)$309MAll assets on the chain, per L2BEAT
Token market cap$182.3MMarket cap rank #197
TVL$14.9MAssets in DeFi protocols
Stablecoins$35.9MUSDT, USDC and others combined
24h DEX volume$1.3M30 days $15.2M
24h fees$36130 days $12K
Block time (measured)4.45 saverage of the last 10K blocks
Stablecoin mix total $35.9M
  • USDT 6% $2.3M
  • USDC 89% $32M
  • Other 4% $1.6M
Top 6 protocols by TVL TVL on this chain
  1. Sygnum FIUSD Liquidity FundRWA$18.3M
  2. SyncSwapDexs$6.2M
  3. Koi Finance AMMDexs$1.2M
  4. LayerZero V2Bridge$1.2M
  5. SpaceFi zkSyncDexs$863K
  6. Aave V3Lending$822K

Sources: CoinGecko (market cap, supply), DefiLlama (TVL, stablecoins, DEX volume, fees, protocols), measurements from public nodes (block time, validators).

The numbers are blunt: only $14.9M locked and $1.3M of 24-hour DEX volume, two or three orders of magnitude below Base and Arbitrum. The bridged assets L2BEAT counts ($309M) are much larger than DeFi locked value, which means most assets simply sit on the chain unused. The ZK token’s market cap is $182.3M.

Strengths and trade-offs

Strengths
  • Correctness is guaranteed by mathematical proof, not by someone watching for errors.
  • In theory withdrawals do not wait for a 7-day challenge period.
  • Native account abstraction allows better wallet experiences (sponsored fees, social recovery).
Trade-offs
  • Little money or activity remains on the chain; the ecosystem is quiet and liquidity is poor.
  • L2BEAT rates it Stage 0: users cannot force transactions if the sequencer halts, and contracts can be upgraded instantly.
  • Although EVM-compatible, it differs from Ethereum underneath, so some contracts and tools need changes to work.
Investigating a project on zkSync? Check these first
  1. 01

    On a thin-liquidity chain a small amount of money can push a price very high; when you see a spike, check how deep the DEX pool is first.

  2. 02

    Confirm whether the token was issued natively on zkSync or bridged in, and which bridge it used.

  3. 03

    Check the permissions on smart contract wallet accounts (who can sign, whether they can be recovered).

Data and sources

  • Live figures: CoinGecko (ZK market cap), DefiLlama, L2BEAT and the official zkSync RPC (measured block time).
  • Mechanisms are based on the official zkSync documentation and L2BEAT’s project page.
  • This guide is educational and is not investment advice.