zkSync Era
$524 M
0.67%
...
Choose token
Ether (ETH)
USD Coin (USDC)
Wrapped BTC (WBTC)
Tether USD (USDT)
Zks (ZKS)
Mute.io (MUTE)
Rocket Pool ETH (rETH)
LUSD Stablecoin (LUSD)
Dai Stablecoin (DAI)
DeversiFi Token (DVF)
Symbiosis (SIS)
Wootrade Network (WOO)
1INCH Token (1INCH)
SHIBA INU (SHIB)
Rocket Pool Protocol (RPL)Milestones
Introduction of Boojum prover
2023 Jul 17th
Deployment of Boojum - new high-performance proof system.
Fair Onboarding Alpha and Rebranding
2023 Feb 16th
zkSync 2.0 rebrands to zkSync Era and lets registered projects and developers deploy on mainnet.
Mainnet for everyone
2022 Mar 24th
Whitelist got removed, there are no restrictions on who can transact with the network.
Description
zkSync Era is a general-purpose ZK Rollup platform from Matter Labs aiming at implementing nearly full EVM compatibility in its ZK friendly custom virtual machine. It implements standard Web3 API and it preserves key EVM features such as smart contract composability while introducing some new concept such as native account abstraction.
If you find something wrong on this page you can submit an issue or edit the information.
Risk analysis
State validation
ZK proofsUses 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.
Upgradeability
YesThe code that secures the system can be changed arbitrarily and without notice by the governor, that currently is a 4 / 8 Multisig. The governor can also change the Verifier contract without notice.
Sequencer failure
Enqueue via L1Users 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 withdrawOnly the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
Rollup stage
zkSync Era is a Technology
Validity proofs ensure state correctness
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.
Zero knowledge SNARK cryptography is used
Despite their production use zkSNARKs are still new and experimental cryptography. Cryptography has made a lot of advancements in the recent years but all cryptographic solutions rely on time to prove their security. In addition zkSNARKs require a trusted setup to operate.
Funds can be stolen if the cryptography is broken or 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 calldata. This ensures that it will always be available when needed.
State derivation
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.
Bytecodes undergo compression before deployment on Layer 1 (L1). You can find additional information on this process here.
There have been neither genesis states nor regenesis.
Details on data format can be found here.
Operator
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.
Withdrawals
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.
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.
Permissions
The system uses the following set of permissioned addresses:
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 zkSync Era Multisig.
This actor is allowed to propose, revert and execute L2 blocks on L1.
Address capable of instant upgrade of the system. Currently set to zero address.
Smart contracts
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: zkSync Era Multisig
Upgrade delay: No delay
Implements ZK proof verification logic.
Can be upgraded by: zkSync Era Multisig
Upgrade delay: No delay
Contract delaying block execution (ie withdrawals and other L2 --> L1 messages).
Value Locked is calculated based on these smart contracts and tokens:
Standard bridge for depositing ERC20 tokens to zkSync Era.
Can be upgraded by: zkSync Era Multisig
Upgrade delay: No delay
Main rollup contract, additionally serving as an escrow.
Can be upgraded by: zkSync Era Multisig
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).
