Search

Search for projects by name or address

Aztec Network logo
Aztec Network

Badges

About

Aztec Network is a privacy-preserving ZK rollup that uses the AztecVM and Noir to support private and public smart contracts on Ethereum.


  • Total Value SecuredTVS
    $647.9450.5%
  • Past day UOPSDaily UOPS
    0.03>1K%
  • Stage
  • Gas token
    AZTEC

  • Type
    ZK Rollup
  • Purposes
    Universal, Privacy
  • Chain ID
    677868

  • Tokens breakdown

    Sequencer failureState validationData availabilityExit windowProposer failure

    Badges

    About

    Aztec Network is a privacy-preserving ZK rollup that uses the AztecVM and Noir to support private and public smart contracts on Ethereum.


    Total
    Canonically BridgedCanonically Bridged ValueCanonical
    Natively MintedNatively Minted TokensNative
    Externally BridgedExternally Bridged ValueExternal

    ETH & derivatives
    Stablecoins
    BTC & derivatives
    Other

    2026 Jul 14 — Aug 07

    Past Day UOPS
    0.03>1K%
    Past Day Ops count
    2.47 K
    Max. UOPS
    0.03
    2026 Jul 25
    Past day UOPS/TPS Ratio
    1.00

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


    2026 Mar 30 — Aug 07


    Total cost
    $283.64 K
    Avg cost per L2 UOP
    $17.360080
    Avg cost per day
    $2.18 K

    This section shows how much data the project publishes to its data-availability (DA) layer over time. The project currently posts data toEthereumEthereum.


    2026 Jul 14 — Aug 07


    Data posted
    3.22 GiB
    Avg size per day
    137.43 MiB
    Avg size per L2 UOP
    206.72 KiB

    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.

    No ongoing anomalies detected

    2026 Jul 08 — Aug 07

    Avg. tx data subs. interval
    1 minute
    Past 30 days anomalies
    100% normal uptime

    Aztec v5 Upgrade

    2026 Jul 14th

    Governance makes v5 canonical which hardens the immutability and fixes vulnerabilities.

    Learn more

    Cut the Leash

    2026 Jun 22nd

    Ownership of the v4 Rollup is revoked, promoting it to Stage 2 (immutable).

    Learn more
    Sequencer failureState validationData availabilityExit windowProposer failure
    Sequencer failure
    Decentralized Sequencer Set

    Users can permissionlessly become a sequencer by staking 200 K AZTEC to join the queue and wait to obtain committee-based block production rights. If the pseudo-randomly sampled committees censor proposals, anyone who bonds 332 M AZTEC will join the escape hatch candidate set. Every 2d 23h, a candidate is pseudo-randomly selected to propose and prove checkpoints fully autonomously. A candidate remains in the set until they are selected or leave voluntarily.

    State validation
    Validity proofs (SN)

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

    Data availability
    Onchain (SD)

    State diffs needed to reconstruct the L2 state are published in Ethereum blobs. Public transaction bodies and client CHONK proofs propagate offchain, so withholding them can prevent permissionless proving; the affected pending checkpoints expire and are pruned rather than finalized.

    Exit window

    Users can exit funds at any time because contracts are not upgradeable. Governance can register a new canonical rollup and bonus-instance validators automatically follow the latest version, but this does not mutate the current instance, its verifier, messaging contracts, or already-installed EscapeHatch. Governance can change bounded validator-entry parameters and can set the GSE proof-of-possession gas limit too low for new deposits; validators explicitly bound to this instance remain on it.

    Proposer failure
    Self Propose

    Checkpoint proposals come from the open sequencer set, with the escape hatch providing a bonded fallback if the sampled committees are censoring or unavailable. Anyone with access to the required hardware can submit epoch root proofs which finalize the proven checkpoints.

    Aztec Network
    Aztec Network is a
    Stage 2
    ZK Rollup.
    The project passes the walkaway test: users can exit in the presence of malicious operators even if the Security Council disappears.

    Learn more about Stages
    Please keep in mind that these stages do not reflect project security, this is an opinionated assessment of project 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.

    All transaction results (state diffs) are published in Ethereum blobs

    Each checkpoint proposal includes EIP-4844 blob commitments for state diffs, checked against the blob hashes in the proposing transaction. The epoch proof revalidates the accumulated commitments before finalization. Public transaction bodies and client CHONK proofs propagate offchain; withholding them can prevent permissionless proving, causing the pending checkpoint to expire and be pruned rather than finalized.

    1. Rollup.sol - propose() on Etherscan
    2. Rollup.sol - validateBlobs() on Etherscan
    Learn more about the DA layer here: Ethereum logoEthereum
    A diagram of the state validation
    A diagram of the state validation

    Each epoch root proof is verified by the HonkVerifier smart contract on Ethereum before the proven checkpoint number is advanced and the epoch outbox