Search
Search for projects by name or address
ZKsync Lite
Badges
About
ZKsync Lite (formerly ZKsync) is a ZK Rollup platform that supports payments, token swaps and NFT minting.
- Compromising ≥75% of the Security Council should be the only way (other than bugs) for a rollup to indefinitely block an L2→L1 message (e.g. a withdrawal) or push an invalid L2→L1 message (e.g. an invalid withdrawal) with a <7d exit window.
Badges
About
ZKsync Lite (formerly ZKsync) is a ZK Rollup platform that supports payments, token swaps and NFT minting.
The section shows the operating costs that L2s pay to Ethereum.
This section shows how "live" the project's operators are by displaying how frequently they submit transactions of the selected type. It also highlights anomalies - significant deviations from their typical schedule.
ZKsync Lite sunsets
2026 May 4th
BlockAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over. production halts for ZKsync Lite, and the orderly sunset process begins.
Funds can be stolen if
Funds can be lost if
Users can be censored if
MEV can be extracted if
Users can force the sequencerA party responsible for ordering and executing transactions on the rollup. The sequencer verifies transactions, compresses the data into a block, and submits the data related to it to enable state reconstruction to Ethereum L1 as a single transaction. The data can be either transaction data or state diffs. to include a transaction by submitting a request through L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development.. If the sequencer censors or is down for for more than 14d, users can use the exit hatch to withdraw their funds.
SNARKs are succinct zero knowledge proofs that ensure state correctness, but require trusted setupGeneration of a piece of data that must then be used for some cryptographic protocol to run. Generating this data requires some secret information. The "trust" comes from the fact the secret must be destroyed after the ceremony, otherwise cryptographic properties of the protocol could be broken. Once the data is generated, and the secrets are forgotten, no further participation from the creators of the ceremony is required. There are two types of trusted setups for SNARKs: (i) trusted setup per circuit where it is generated from scratch for each circuit, (ii) trusted universal setup per proving system where it can be used for several circuits..
All of the data needed for proof construction is published on Ethereum L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development..
Users have 7d to exit funds in case of an unwanted non-emergency upgrade. There is a 21d delay before a non-emergency upgrade is applied, and withdrawals can take up to 14d to be processed.
There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.
Users are able to trustlessly exit by submitting a zero knowledge proof of funds.
Rollup operators cannot compromise the system, but being application-specific might bring additional risk.
ZKsync Lite provides the infrastructure for token transfer, swaps and NFT minting. Arbitrary contracts are not supported.
All data required for proofs is published onchain
All the data that is used to construct the system state is published onchain in the form of cheap calldata. This ensures that it will always be available when needed.
EthereumNo compression, transactions are always the same size.
There is no genesis file nor regenesis for ZKsync Lite. By default, all accounts were empty at the beginning.
The data format documentations can be found here.
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.
2026 July 23, 11:36 UTC1changeRotated one Matter Labs ms member.
Rotated one Matter Labs ms member.
| contract Matter Labs Multisig (eth:0x4e4943346848c4867F81dFb37c4cA9C5715A7828) [GnosisSafe] { | |
| +++ description: None | |
| values.$members.2: | |
| - | "eth:0x5C7E59Dba6557C7dAB3B69ccd3E309d1965Cf1B1" |
| + | "eth:0xC9A814A4dFE108A4d2b0C01abb4c196Ed7FB3D83" |
| } | |
2026 July 22, 10:12 UTC11changesDowngraded 5/8 owner multisig to 1/1. Note that the project is already sunset and entered the shutdown phase.
Downgraded 5/8 owner multisig to 1/1. Note that the project is already sunset and entered the shutdown phase.
| contract ZkSync Multisig (eth:0xE24f4870Ab85DE8E356C5fC56138587206c70d99) [GnosisSafe] { | |
| +++ description: None | |
| values.$members.0: | |
| - | "eth:0x4964D00fA975a7346ee6196a94b07c01ed1cD3CE" |
| values.$members.1: | |
| - | "eth:0x050b37a12451F188c7bA53D48b8A1adE6D138E71" |
| values.$members.2: | |
| - | "eth:0xeF4CcBDf8f91A001164149558106737A568e4912" |
| values.$members.3: | |
| - | "eth:0xC9474de11503D63D892cEDD12d6B93f6A25a9cbF" |
| values.$members.4: | |
| - | "eth:0x45F9AfCf9565051344aFb36e665f4d7bb2d18415" |
| values.$members.5: | |
| - | "eth:0x702caCafA54B88e9c54449563Fb2e496e85c78b7" |
| values.$members.6: | |
| - | "eth:0xD613b3a3924D0dE9B4a352ca0669e743cBC3C4AA" |
| values.$members.7: | |
| - | "eth:0x3068415e0F857A5eEd03302A1F7E44f67468d2Bc" |
| + | "eth:0x4e4943346848c4867F81dFb37c4cA9C5715A7828" |
| values.$threshold: | |
| - | 5 |
| + | 1 |
| values.multisigThreshold: | |
| - | "5 of 8 (63%)" |
| + | "1 of 1 (100%)" |
| } | |
| + | Status: CREATED |
| contract Matter Labs Multisig (eth:0x4e4943346848c4867F81dFb37c4cA9C5715A7828) [GnosisSafe] | |
| +++ description: None | |
2026 May 12, 10:07 UTC15changesPaused deposits to zksync. Upgraded zksync contract by adding token migration to claim distributor: https://disco.l2beat.com/diff/eth:0x8e972b354E6933275513C355Ee14D44A832aD2d9/eth:0x803B96fA3cE086A722CB6C1e2C79D304c8a263Ff. More precisely, added: - l1ClaimDistributor . It's supposed to store Merkle root of all toknes claimRoot and let users permissionlessly claim their funds agains the root - pauseDeposits function that permanently halts deposits into zksync L2 - setClaimRoot function that sets withdrawal smart contracts and activates exodus mode - migrateToken function that transfers given token to the registered claim distributor contract. Deposits to L2 were halted, claim distributor contract was set to 0x0a14B696350546110a0D8acDb86226983af9D2a0, exodus mode activated and several tokens were migrated to the claim contract. In the exodus mode, tokens could not be deposited and withdrawn, new blocks could not be committed, proven or executed. Config: use the new flattener implementation.
Paused deposits to zksync. Upgraded zksync contract by adding token migration to claim distributor: https://disco.l2beat.com/diff/eth:0x8e972b354E6933275513C355Ee14D44A832aD2d9/eth:0x803B96fA3cE086A722CB6C1e2C79D304c8a263Ff. More precisely, added:
l1ClaimDistributor. It’s supposed to store Merkle root of all toknesclaimRootand let users permissionlessly claim their funds agains the rootpauseDepositsfunction that permanently halts deposits into zksync L2setClaimRootfunction that sets withdrawal smart contracts and activates exodus modemigrateTokenfunction that transfers given token to the registered claim distributor contract.
Deposits to L2 were halted, claim distributor contract was set to 0x0a14B696350546110a0D8acDb86226983af9D2a0, exodus mode activated and several tokens were migrated to the claim contract. In the exodus mode, tokens could not be deposited and withdrawn, new blocks could not be committed, proven or executed.
Config: use the new flattener implementation.
| contract Multisig 3 (eth:0x225d3822De44E58eE935440E0c0B829C4232086e) [GnosisSafe] { | |
| +++ description: None | |
| values.$members.2: | |
| - | "eth:0xB1A308e7F02798377b7acF685E997E3D774c5863" |
| + | "eth:0xd6970196Ff8CeF3Cdd61256C1841A085EEcD3ae8" |
| } | |
| contract UpgradeGatekeeper (eth:0x38A43F4330f24fe920F943409709fc9A6084C939) [N/A] { | |
| +++ description: None | |
| values.versionId: | |
| - | 12 |
| + | 13 |
| } | |
| contract ZkSync (eth:0xaBEA9132b05A70803a4E85094fD0e1800777fBEF) [N/A] { | |
| +++ description: None | |
| sourceHashes.1: | |
| - | "0xc9d63ef2a845873ca1ad004f9cf86cd0d77ee4a37cca41132c0dea73d460ea1c" |
| + | "0xb50bdd92f62f1f18bc1e695c5a1cb0467f936a3e8702454a02e5ef54c6f1e9a2" |
| values.$implementation.0: | |
| - | "eth:0x8e972b354E6933275513C355Ee14D44A832aD2d9" |
| + | "eth:0x803B96fA3cE086A722CB6C1e2C79D304c8a263Ff" |
| values.$implementation.1: | |
| - | "eth:0x2eaa1377e0fC95dE998B9fA7611E9D67ebA534fD" |
| + | "eth:0xBF8ee0141203A7986142000B85f7afaBeee1279d" |
| values.exodusMode: | |
| - | false |
| + | true |
| values.l1ClaimDistributor: | |
| + | "eth:0x0a14B696350546110a0D8acDb86226983af9D2a0" |
| values.pausedDeposits: | |
| + | true |
| errors: | |
| - | {"l1ClaimDistributor":"Processing error occurred.","migratedTokens":"Processing error occurred."} |
| implementationNames.eth:0x8e972b354E6933275513C355Ee14D44A832aD2d9: | |
| - | "ZkSync" |
| implementationNames.eth:0x2eaa1377e0fC95dE998B9fA7611E9D67ebA534fD: | |
| - | "AdditionalZkSync" |
| implementationNames.eth:0x803B96fA3cE086A722CB6C1e2C79D304c8a263Ff: | |
| + | "ZkSync" |
| implementationNames.eth:0xBF8ee0141203A7986142000B85f7afaBeee1279d: | |
| + | "AdditionalZkSync" |
| } | |
| + | Status: CREATED |
| contract ZkSyncLiteSunsetClaimDistributorL1 (eth:0x0a14B696350546110a0D8acDb86226983af9D2a0) [N/A] | |
| +++ description: Distributor smart contract that holds tokens migrated from zksync lite rollup contract and allows users withdrawing them. | |
| + | Status: CREATED |
| contract ProxyAdmin (eth:0xDc7009bCAabD4069391C0aa9445D58a759fE1c7d) [global/ProxyAdmin] | |
| +++ description: None | |
2026 March 20, 15:22 UTC1changeRotated ms member.
Rotated ms member.
| contract ZkSync Multisig (eth:0xE24f4870Ab85DE8E356C5fC56138587206c70d99) { | |
| +++ description: None | |
| values.$members.2: | |
| - | "eth:0x37A71E0C1A5808343D893Db40e12A74e0A387908" |
| + | "eth:0xeF4CcBDf8f91A001164149558106737A568e4912" |
| } | |
2025 December 29, 11:33 UTCHigh severity10changesUpgraded Safe multisig to version 1.4.1. Also rotated one multisig member, added a new one and increased the threshold.
Upgraded Safe multisig to version 1.4.1. Also rotated one multisig member, added a new one and increased the threshold.
| contract Multisig 3 (eth:0x225d3822De44E58eE935440E0c0B829C4232086e) { | |
| +++ description: None | |
| sourceHashes.1: | |
| - | "0xd42bbf9f7dcd3720a7fc6bdc6edfdfae8800a37d6dd4decfa0ef6ca4a2e88940" |
| + | "0x7d388119a66f3eae147d748f86136f073d907d6b36f7e87e9363c4c7a2899a8a" |
| values.$implementation: | |
| - | "eth:0xd9Db270c1B5E3Bd161E8c8503c55cEABeE709552" |
| + | "eth:0x41675C099F32341bf84BFc5382aF534df5C7461a" |
| values.$members.0: | |
| + | "eth:0xD8A6A3ca1739423de5F634dFAa8BA224EAf16d0e" |
| values.$members.1: | |
| + | "eth:0x223c0EF36fEe905a40175d92704b1d3624218EE7" |
| values.$members.1: | |
| - | "eth:0x0d4E989c7620C8749c9417d2BF218896C767B606" |
| values.$threshold: | |
| - | 2 |
| + | 3 |
| values.multisigThreshold: | |
| - | "2 of 3 (67%)" |
| + | "3 of 4 (75%)" |
| values.VERSION: | |
| - | "1.3.0" |
| + | "1.4.1" |
| implementationNames.eth:0xd9Db270c1B5E3Bd161E8c8503c55cEABeE709552: | |
| - | "GnosisSafe" |
| implementationNames.eth:0x41675C099F32341bf84BFc5382aF534df5C7461a: | |
| + | "Safe" |
| } | |
The system has a centralized operator
The operatorAn operator is the entity charged with managing a rollup and progressing its state. A rollup operator can be a centralized sequencer, proposer, prover, challenger, pauser of admin that is able to perform upgrades. is the only entity that can propose blocksAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over.. 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 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 onchain. 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. However, there exists a mechanism to independently exit the system.
Regular exit
The user initiates the withdrawal by submitting a regular transaction on this chain. When the blockAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over. containing that transaction is settled the funds become available for withdrawal on L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development.. ZK proofs are required to settle blocks. Finally the user submits an L1 transaction to claim the funds.
Forced exit
If the user experiences censorship from the operatorAn operator is the entity charged with managing a rollup and progressing its state. A rollup operator can be a centralized sequencer, proposer, prover, challenger, pauser of admin that is able to perform upgrades. with regular exit they can submit their withdrawal requests directly on L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development.. The system is then obliged to service this request. Once the force operation is submitted and if the request is serviced, the operation follows the flow of a regular exit.
Emergency exit
If the enough time deadline 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 L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development. transaction.
Funds can be lost if the user is unable to generate the non-trivial ZK proof for exodus withdraw.
Ethereum
Actors:
A Multisig with 1/1 threshold. This Multisig is the owner of Upgrade Gatekeeper contract and therefore is allowed to perform upgrades for Governance, VerifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover. and ZkSync contracts. It can also change the list of active validatorsIn the context of L2s, a Validator is an actor that validates the correctness of state transitions. For optimistic rollups this corresponds to challengers, and for ZK rollups this corresponds to the onchain verifier and appoint the security councilA Security Council is a sufficiently decentralized set of members that is able to upgrade a system. A properly set up Security Council consists of at least 8 members with a threshold greater than 75%. What 'sufficiently decentralized' means is fundamentally subjective and L2BEAT evaluates each case individually. A Security Council is allowed to instantly upgrade Stage 1 rollups. (by upgrading the ZkSync contract).
Participants (1):
0x4e49…7828The Security CouncilA Security Council is a sufficiently decentralized set of members that is able to upgrade a system. A properly set up Security Council consists of at least 8 members with a threshold greater than 75%. What 'sufficiently decentralized' means is fundamentally subjective and L2BEAT evaluates each case individually. A Security Council is allowed to instantly upgrade Stage 1 rollups.’s only role is to reduce the upgrade delay to zero if 9 of its members decide to do so. The council has 15 members which are hardcoded into the ZkSync contract. Changing the council requires a ZkSync contract upgrade.
Those actors are allowed to propose, revert and execute L2Layer 2 (L2) is a category of technical solutions aimed to scale the base layer in a trust minimized way. This category includes solutions like rollups as well as state channels and plasma. Other solutions are able to scale further, but with the introduction of additional trust assumptions, which are therefore not trust minimized. Sometimes the term Layer 2 is used to refer to include these solutions too, like validiums and optimiums, but to distinguish between trust minimized and non trust minimized solutions they are often referred to as "light" L2s, opposed to "strong" L2s like rollups. blocksAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over. on L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development..
Account receiving fees for listing tokens. Can be updated by ZkSync Multisig.
Ethereum
The main RollupA blockchain that inherits consensus and data availability from another blockchain called L1. Rollups enable trust minimized bridges with the base layer via proof systems, either optimistic or zero-knowledge. A rollup without a bridge, or without considering the bridge, is called a sovereign rollup. contract. Allows the operatorAn operator is the entity charged with managing a rollup and progressing its state. A rollup operator can be a centralized sequencer, proposer, prover, challenger, pauser of admin that is able to perform upgrades. to commit blocksAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over., provide ZK proofs (validated by the VerifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover.) and processes withdrawals by executing blocks. Users can deposit ETH and ERC20 tokens. This contract also defines the upgrade process for all the other contracts by enforcing an upgrade delay and employing the Security CouncilA Security Council is a sufficiently decentralized set of members that is able to upgrade a system. A properly set up Security Council consists of at least 8 members with a threshold greater than 75%. What 'sufficiently decentralized' means is fundamentally subjective and L2BEAT evaluates each case individually. A Security Council is allowed to instantly upgrade Stage 1 rollups. which can shorten upgrade times.
All supported tokens in this escrow are included in the value secured calculation.
Implements ZK proof verification logic.
Keeps a list of blockAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over. producers, NFT factories and whitelisted tokens.
This is the contract that owns Governance, VerifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover. and ZkSync and facilitates their upgrades. The upgrade constraints are defined by the ZkSync contract.
Allows anyone to add new ERC20 tokens to ZKsync Lite given sufficient payment.
Allows for withdrawing NFTs minted on L2Layer 2 (L2) is a category of technical solutions aimed to scale the base layer in a trust minimized way. This category includes solutions like rollups as well as state channels and plasma. Other solutions are able to scale further, but with the introduction of additional trust assumptions, which are therefore not trust minimized. Sometimes the term Layer 2 is used to refer to include these solutions too, like validiums and optimiums, but to distinguish between trust minimized and non trust minimized solutions they are often referred to as "light" L2s, opposed to "strong" L2s like rollups. to L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development..
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).