Search

Search for projects by name

SummaryValue SecuredOnchain costsLivenessMilestones & IncidentsRisk summaryRisk analysisRollup stageData availabilityState validationOperatorWithdrawalsPermissionsSmart contracts

ZKBase logoZKBase

Badges

About

ZKBase is an infrastructure protocol based on Zero-Knowledge (ZK) proof technology. It aims to support various projects across the Bitcoin and Ethereum networks.

Value secured
$412.29 K21.9%
Canonically Bridged
$412.29 K
Natively Minted
$0.00
Externally Bridged
$0.00
View TVS Breakdown
  • Tokens
  • Past day UOPS
    No data
  • 30D ops count
    No data
  • Stage
  • Type
    ZK Rollup
  • Purposes
    NFT, Exchange, Payments
    • Sequencer failureState validationData availabilityExit windowProposer failure
    Explore more in Discovery UI

    Badges

    About

    ZKBase is an infrastructure protocol based on Zero-Knowledge (ZK) proof technology. It aims to support various projects across the Bitcoin and Ethereum networks.

    Value Secured

    2024 May 24 — 2025 May 24

    Total value securedTotal
    $412.29 K21.9%
    Canonically BridgedCanonically Bridged ValueCanonical
    $412.29 K21.9%
    Natively MintedNatively Minted TokensNative
    $0.000.00%
    Externally BridgedExternally Bridged ValueExternal
    $0.000.00%
    View TVS breakdown
    Onchain costs

    The section shows the operating costs that L2s pay to Ethereum.

    2024 May 24 — 2025 May 13

    1 year total cost
    $1.07 K
    Avg cost per L2 UOP
    No data
    Liveness

    The chart illustrates how "live" the project's operators are by displaying how frequently they submit transactions of the selected type and if these intervals deviate from their typical schedule.

    2025 May 12 — 13

    30D avg. proof subs. interval
    17 days
    30D avg. state updates interval
    17 days
    Past 30 days anomalies
    Milestones & Incidents

    ZKSpace Officially Upgrades to ZKBase

    2023 Dec 29th

    The ZKSpace team has rebranded to ZKBase.

    Learn more

    Token Deposit Campaign started

    2022 Feb 21st

    Incentives program to onboard new users has started.

    Learn more
    Risk summary

    Funds can be lost if

    1. the user is unable to generate the non-trivial ZK proof for exodus withdraw.

    Users can be censored if

    1. the operator refuses to include their transactions. However, there exists a mechanism to independently exit the system.

    MEV can be extracted if

    1. the operator exploits their centralized position and frontruns user transactions.
    Risk analysis
    Sequencer failureState validationData availabilityExit windowProposer failure
    Sequencer failure
    Force via L1

    Users can force the sequencer to include a withdrawal transaction by submitting a request through L1. If the sequencer censors or is down for for more than 3d, users can use the exit hatch to withdraw their funds.

    State validation
    ZK proofs (SN)

    SNARKs are zero knowledge proofs that ensure state correctness, but require trusted setup.

    Data availability
    Onchain

    All of the data needed for proof construction is published on Ethereum L1.

    Exit window
    5d

    Users have 5d to exit funds in case of an unwanted regular upgrade. There is a 8d delay before a regular upgrade is applied, and withdrawals can take up to 3d to be processed.

    Proposer failure
    Use escape hatch

    Users are able to trustlessly exit by submitting a zero knowledge proof of funds.

    Rollup stageZKBaseZKBase is a
    Stage 0
    Appchain
    ZK Rollup.

    Rollup operators cannot compromise the system, but being application-specific might bring additional risk.

    ZKBase provides the infrastructure for token transfer, swaps and NFT minting. Arbitrary contracts are not supported.

    Note:
    We're still in the process of formalizing how to properly integrate appchains in the Stages framework.
    There is no available node software that can reconstruct the state from L1 data, hence there is no way to verify that this system is a rollup.

    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.
    Data availability

    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.

    1. ZKSwap Introduces Practical ZK Rollups - Medium blog
    Learn more about the DA layer here: Ethereum logoEthereum
    State validation
    Validity proofs

    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.

    1. ZKSwap Introduces Practical ZK Rollups - Medium blog
    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. ZKSwap Validator - ZKSwap wiki

    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.

    1. ZkSync.sol#L404 - ZKSwap source code
    Withdrawals

    Regular exit

    The user initiates the withdrawal by submitting a regular transaction on this chain. When the block containing that transaction is settled the funds become available for withdrawal on L1.ZK proofs are required to settle blocks. Finally the user submits an L1 transaction to claim the funds.

    1. Make Transaction

    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 and if the request is serviced, the operation follows the flow of a regular exit.

    1. ZkSync.sol#L404 - ZKSwap source code

    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 L1 transaction.

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

    1. ZkSyncCommitBlock.sol#L230-L246 - ZKSwap source code
    Permissions
    A dashboard to explore contracts and permissions
    Go to Disco
    Disco UI Banner
    Disco UI BannerExplore in Disco

    Ethereum

    Actors:

    zkSpace Admin 0xfCAE…05Be

    This address is the master of Upgrade Gatekeeper contract, which is allowed to perform upgrades for Governance, Verifier, VerifierExit, PairManager, ZkSeaNFT and ZkSync contracts.

    Active validator 0x5bd9…41E2

    This actor is allowed to propose, revert and execute L2 blocks on L1. A list of active validators is kept inside Governance contract and can be updated by zkSpace Admin.

    Smart contracts
    A dashboard to explore contracts and permissions
    Go to Disco
    Disco UI Banner
    Disco UI BannerExplore in Disco
    A diagram of the smart contract architecture
    A diagram of the smart contract architecture

    Ethereum

    ZkSync 0x5CDA…3Be8Implementation #1 (Upgradable)Implementation #2 (Upgradable)Implementation #3 (Upgradable)Implementation #4 (Upgradable)Admin

    The main Rollup contract. Operator commits blocks, provides ZK proof 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 that is currently set to 8 days.

    • This contract can store any token.
    Can be upgraded by:
    zkSpace Admin with 8d delay
    Governance 0x83Cb…fB89Implementation (Upgradable)Admin

    Keeps a list of block producers and whitelisted tokens.

    Can be upgraded by:
    zkSpace Admin with 8d delay
    UniswapV2Factory 0xc07f…3735Implementation (Upgradable)Admin

    Manages trading pairs.

    Can be upgraded by:
    zkSpace Admin with 8d delay
    ZkSeaNFT 0xc632…95b5Implementation (Upgradable)Admin

    Contract managing deposits and withdrawals of NFTs to ScalingProject.

    Can be upgraded by:
    zkSpace Admin with 8d delay
    UpgradeGatekeeper 0xB0C7…1390

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

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

    The current deployment carries some associated risks:

    • Funds can be stolen if a contract receives a malicious code upgrade. There is a 8d delay on code upgrades.