zkSync logozkSync


...


Tokens:

Milestones
zkEVM alpha
2022 Oct 28th
Deployment of the system to mainnet, for the testing purposes.
zkSync 1.0 launch
2020 Jun 18th
zkSync is live, bringing trustless, scalable payments to Ethereum using zkRollup technology.

Description

zkSync is a user-centric zk rollup platform from Matter Labs. It is a scaling solution for Ethereum, already live on Ethereum mainnet. It supports payments, token swaps and NFT minting.

If you find something wrong on this page you can submit an issue or edit the information.

Risk summary

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. Once the proof is processed on the Ethereum blockchain the L2 block is instantly finalized.

  1. Validity proofs - zkSync FAQ

Zero knowledge SNARK cryptography is used

Despite their production use ZK-SNARKs 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 ZK-SNARKs require a trusted setup to operate.

  • Funds can be stolen if the cryptography is broken or implemented incorrectly.

  1. Cryptography used - zkSync FAQ

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.

  1. Overview - zkSync documentation

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.

  1. How decentralized is zkSync - zkSync FAQ

Users can force exit the system

Force exit allows the users to escape censorship by withdrawing their funds. The system allows users to force the withdrawal of funds by submitting a request directly to the contract on-chain. The request must be served within a defined time period. If this does not happen, the system will halt regular operation and permit trustless withdrawal of funds.

  • Users can be censored if the operator refuses to include their transactions. They can still exit the system.

  1. Priority queue - zkSync FAQ

Withdrawals

Regular exit

The user initiates the withdrawal by submitting a transaction on L2. 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 does not require 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. Once the force operation is submitted if the request is serviced the operation follows the flow of a regular exit.

  1. Withdrawing funds - zkSync documentation

Emergency exit

If enough time passes and the forced exit is still ignored the user can put the system into Exodus Mode, disallowing further state updates. In that case everybody can withdraw by submitting a zero knowledge proof of their funds with their L1 transaction.

  • Funds can be lost if the user is unable to generate the non-trivial zk proof for exodus withdraw.

  1. Withdrawing funds - zkSync documentation
  2. README.md - zkSync Exit Tool

Permissioned Addresses

The system uses the following set of permissioned addresses:

zkSync MultiSig 0xE24f…0d99

This MultiSig is the master of Upgrade Gatekeeper contract, which is allowed to perform upgrades for Governance, Verifier and ZkSync contracts. It can change the list of active validators.

These addresses are the participants of the 3/6 zkSync MultiSig.

By default upgradeable contracts can be upgraded only after 3 weeks period. Security council can vote to cut this period to 0 days making the upgrade possible immediately if at least 9 out of 15 counselors agree on this.

Active validator 0x01c3…F91e

This actor is allowed to propose, revert and execute L2 blocks on L1.

Token listing beneficiary 0x2A0a…d027

Account receiving fees for listing tokens. Can be updated by zkSync MultiSig.

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 zkProof which is validated by the Verifier contract and process withdrawals (executes blocks). Users deposit ETH and ERC20 tokens. This contract defines the upgrade delay in the UPGRADE_NOTICE_PERIOD constant is currently set to 21 days. 9/15 Security Council MSig can override the delay period and execute an emergency immediate upgrade. This contract can store any token

Implements zkProof verification logic.

UpgradeGatekeeper 0x38A4…C939

This is the contract that implements the upgrade mechanism for Governance, Verifier and ZkSync. It relies on the ZkSync contract to enforce upgrade delays.

Keeps a list of block producers, NFT factories and whitelisted tokens.

The current deployment carries some associated risks:

  • Funds can be stolen if a contract receives a malicious code upgrade. There is a 21 days or 0 if overridden by 9/15 MSig delay on code upgrades.