zkSync Era logozkSync Era

zkSync Era is a general-purpose ZK Rollup with full EVM compatibility.
Value Locked

$882.51 M


Canonically Bridged
$810.83 M
Externally Bridged
$2.29 M
Natively Minted
$69.37 M
  • Tokens
  • Daily TPS
  • 30D tx count
    24.78 M
  • Stage
    Stage 0
  • Type
    ZK Rollup
  • Purpose
  • ...




    zkSync Era starts using blobs

    2024 Mar 13th

    zkSync Era starts publishing data to blobs.

    Learn more

    Introduction of Boojum prover

    2023 Jul 17th

    Deployment of Boojum - new high-performance proof system.

    Learn more

    Full Launch Alpha

    2023 Mar 24th

    zkSync Era is now permissionless and open for everyone.

    Learn more

    Fair Onboarding Alpha and Rebranding

    2023 Feb 16th

    zkSync 2.0 rebrands to zkSync Era and lets registered projects and developers deploy on mainnet.

    Learn more

    zkSync 2.0 baby alpha launch

    2022 Oct 28th

    zkSync 2.0 baby alpha is launched on mainnet.

    Learn more
    Risk summary
    Withdrawals are delayed by 21h. The length of the delay can be arbitrarily set by a MultiSig.
    Risk analysis
    Withdrawals are delayed by 21h. The length of the delay can be arbitrarily set by a MultiSig.
    Sequencer failureState validationData availabilityExit windowProposer failure

    State validation

    ZK proofs

    Uses PLONK zero-knowledge proof system with KZG commitments.

    Data availability

    On chain (SD)

    All of the data (SD = state diffs) needed for proof construction is published on chain.

    Exit window


    There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.

    Sequencer failure

    Enqueue via L1

    Users can submit transactions to an L1 queue, but can’t force them. The sequencer cannot selectively skip transactions but can stop processing the queue entirely. In other words, if the sequencer censors or is down, it is so for everyone.

    Proposer failure

    Cannot withdraw

    Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.

    Rollup stage
    zkSync ErazkSync Era is a
    Stage 0
    ZK Rollup.
    Stage 0
    4 requirements met
    Stage 1
    2 issues need fixing
    Stage 2
    1 issue needs fixing
    Learn more about Rollup stages
    Please keep in mind that these stages do not reflect rollup security, this is an opinionated assessment of rollup maturity based on subjective criteria, created with a goal of incentivizing projects to push toward better decentralization. Each team may have taken different paths to achieve this goal.

    Zero knowledge STARK and SNARK cryptography is used

    Despite their production use zkSTARKs and zkSNARKs proof systems are still relatively new, complex and they rely on the proper implementation of the polynomial constraints used to check validity of the Execution Trace. In addition zkSNARKs require a trusted setup to operate.

    • Funds can be lost if the proof system is implemented incorrectly.

    All data required for proofs is published on chain

    All the data that is used to construct the system state is published on chain in the form of cheap blobs or calldata. This ensures that it will be available for enough time.

    State derivation
    Node software

    The node software is open-source, and its source code can be found here. The main node software does not rely on Layer 1 (L1) to reconstruct the state, but you can use this tool for that purpose. Currently, there is no straightforward method to inject the state into the main node, but zkSync is actively working on a solution for this.

    Compression scheme

    Bytecodes undergo compression before deployment on Layer 1 (L1). You can find additional information on this process here.

    Genesis state

    There have been neither genesis states nor regenesis.

    Data format

    Details on data format can be found here.

    State validation

    Each update to the system state must be accompanied by a ZK proof that ensures that the new state was derived by correctly applying a series of valid user transactions to the previous state. These proofs are then verified on Ethereum by a smart contract.

    Prover Architecture

    zkSync Era proof system Boojum can be found here and contains essential tools like the Prover, the Verifier, and other backend components. The specs of the system can be found here.

    ZK Circuits

    zkSync Era circuits are built from Boojum and are designed to replicate the behavior of the EVM. The source code can be found here. The circuits are checked against tests that can be found here.

    • Funds can be lost if the proof system is implemented incorrectly.

    Verification Keys Generation

    SNARK verification keys can be generated and checked against the Ethereum verifier contract using this tool. The system requires a trusted setup.


    The system has a centralized operator

    The operator is the only entity that can propose blocks. A live and trustworthy operator is vital to the health of the system.

    • MEV can be extracted if the operator exploits their centralized position and frontruns user transactions.

    Users can force any transaction via L1

    If a user is censored by L2 Sequencer, they can try to force transaction via L1 queue. Right now there is no mechanism that forces L2 Sequencer to include transactions from L1 queue in an L1 block.

    • Users can be censored if the operator refuses to include their transactions.

    1. L1 - L2 interoperability - Developer's documentation

    Regular exit

    The user initiates the withdrawal by submitting a regular transaction on this chain. When the block containing that transaction is proven the funds become available for withdrawal on L1. Finally the user submits an L1 transaction to claim the funds. This transaction requires a merkle proof.

    1. Withdrawing funds - zkSync documentation

    Forced exit

    If the user experiences censorship from the operator with regular exit they can submit their withdrawal requests directly on L1. The system is then obliged to service this request or halt all messages from L1, including all forced withdrawals and deposits. Once the force operation is submitted and if the request is serviced, the operation follows the flow of a regular exit.

    Upgrades & Governance
    A diagram of the upgrades and governance
    A diagram of the upgrades and governance

    Currently, the Matter Labs multisig (4 / 8) is able to instantly upgrade all contracts (including the diamond and its facets) and roles (including the Governor role). The Governor role that resolves to the multisig is the highest permissioned role defined in the system.

    Governor: Can access all AdminFacet functions and thus upgrade the diamond and the related smart contract system. Additionally inherits access to functions for the Admin role. Can freeze all freezable Facets (currently ExecutorFacet, MailboxFacet) and upgrade the bridges.

    Validator: Proposes batches from L2 into the ValidatorTimelock, from where they can be proven and finally executed (through the ExecutorFacet of the diamond) after a predefined delay (currently 21h). This allows for freezing the L2 chain within the delay if any suspicious activity was detected. Can be set by the Admin or Governor.

    Verifier: Verifies the zk proofs that were provided by the Validator. Can be changed by calling ExecuteUpgrade() on the AdminFacet from the Governor role.

    Admin: Currently not set. Will be able to make non-critical changes like setting the Validator. Will be the role of the multisig when higher permissions are restricted to the Security Council.

    Security Council: Currently not set. Will share the Governor role of the main diamond with the Matter Labs multisig through the Governance smart contract (see below).

    A Governance smart contract is set up as the Governor role of the diamond. It includes logic for planning upgrades with parameters like transparency and/or a delay. Currently the delay is optional (minimum delay = 0s) and not used by the multisig. The optional transparency may be used in the future to hide instant emergency upgrades by the Security Council or delay transparent (thus auditable) governance upgrades. The Governance smart contract has two roles, an owner role and a securityCouncil role.


    The system uses the following set of permissioned addresses:

    Matter Labs Multisig 0x4e49…7828

    This MultiSig is the current Governor of zkSync Era main contract and owner of the L1EthBridge. It can upgrade zkSync Era, upgrade bridge, change rollup parameters with no delay. This is a Gnosis Safe with 4 / 8 threshold.

    Those are the participants of the Matter Labs Multisig.

    Those actors are allowed to propose, revert and execute L2 blocks on L1.

    Smart contracts
    A diagram of the smart contract architecture
    A diagram of the smart contract architecture

    The system consists of the following smart contracts:

    The main Rollup contract. Operator commits blocks, provides ZK proof which is validated by the Verifier contract and process transactions (executes blocks). During block execution it processes L1 --> L2 and L2 --> L1 transactions. It uses separate Verifier to validate ZK proofs. Governance manages list of Validators and can set basic rollup parameters. It is also serves the purpose of ETH bridge. This contract stores the following tokens: ETH.

    Can be upgraded by: Matter Labs Multisig

    Upgrade delay: No delay

    Verifier 0xdd9C…7Ed2

    Implements ZK proof verification logic.

    Can be upgraded by: Matter Labs Multisig

    Upgrade delay: No delay

    ValidatorTimelock 0xa8CB…c1bD

    Contract delaying block execution (ie withdrawals and other L2 --> L1 messages).

    Governance 0x0b62…3F61

    Owner can schedule a transparent (you see the upgrade data on-chain) or a shadow (you don’t see the upgrade data on-chain) upgrade. While scheduling an upgrade the owner chooses a delay, that delay has to be bigger than 0 seconds. Canceling the upgrade can be done only by the owner. The owner or the security council can perform the upgrade if the chosen delay is up. Only the security council can force the upgrade to execute even if the delay is not up.

    Can be upgraded by: Matter Labs Multisig

    Upgrade delay: No delay

    Value Locked is calculated based on these smart contracts and tokens:

    Standard bridge for depositing ERC20 tokens to zkSync Era.

    Can be upgraded by: Matter Labs Multisig

    Upgrade delay: No delay

    Escrow for ETH 0x3240…0324

    Main rollup contract, additionally serving as an escrow.

    Can be upgraded by: Matter Labs Multisig

    Upgrade delay: No delay

    Bridge for depositing wrapped stETH (Lido) to zkSync Era.

    Can be upgraded by: Lido (Lido Agent)

    Upgrade delay: No delay

    The current deployment carries some associated risks:

    • Funds can be stolen if a contract receives a malicious code upgrade. There is no delay on code upgrades (CRITICAL).

    Knowledge nuggets