Zircuit
  • Introduction
  • Frequently Asked Questions (FAQ)
  • Tokenomics
    • Zircuit Token (ZRC)
    • Bridging ZRC to Zircuit
  • Build on Zircuit
    • Quick Start
    • Deploy on Zircuit
    • Zircuit LST/LRT Liquidity Hub
  • Architecture and Concepts
    • Architecture
      • Modular Prover Design
      • Template Proofs
      • Versions and Updates
    • Concepts
    • Sequencer Level Security (SLS)
    • Gas Pricing and Transaction Fees
    • Transaction Statuses
    • Supported Transaction Types
  • Research
    • Research
    • Publications and Grants
    • Talks and Panels
  • Dev Tools
    • Block Explorer
    • RPC Endpoints
    • Bridge
    • Verifying Contracts
    • ERC20 Tokens with Zircuit Canonical Bridge
    • Development Frameworks
    • CREATE2 Deployments
    • Oracles
    • Indexing and Subgraph
    • Relayers
    • Unsupported Opcodes
    • Precompiles
    • L1 Data Fee Calculation
  • Smart Contracts
    • L1 Contracts
    • L2 Contracts
    • Contract Addresses
    • Bridged Token Addresses
  • Security
    • Security
    • Privileged Roles
    • Bug Bounty
    • Audit Reports
  • Garfield Testnet
    • Garfield Testnet Quick Start
    • Garfield Testnet Bridging Prerequisites
      • Adding the Sepolia Network To Metamask
      • Adding The Zircuit Garfield Testnet Network To Metamask
      • Connecting Metamask To Zircuit’s Bridge
    • Deploy on the Zircuit Garfield Testnet
    • RPC Endpoints
    • Block Explorer
    • Verifying Contracts
    • Bridge
    • Faucet
    • Differences & Limitations
    • Contract Addresses
  • Testnet Legacy
    • Legacy Testnet Quick Start
    • Legacy Testnet Bridging Prerequisites
      • Adding The Sepolia Network To Metamask
      • Adding The Zircuit Legacy Testnet Network To Metamask
      • Connecting Metamask To Zircuit’s Bridge
    • Deploy on the Legacy Zircuit Testnet
    • RPC Endpoints
    • Block Explorer
    • Verifying Contracts
    • Bridge
    • Faucet
    • Contract Addresses
  • Bridging Step-by-Step
    • Prequisites
      • Adding The Zircuit Network To Metamask
    • Bridging From Sepolia To Zircuit
    • Bridging From Zircuit To Sepolia
    • Completing Withdrawals From Zircuit
    • Bridging ERC20 Tokens Manually
    • Binance Web3 Wallet Task Tutorial
      • Binance Web3 Wallet Tutorial: Bridging back to Ethereum
    • Exploring Bridging Behaviors with EIP-7702
Powered by GitBook
On this page
  • What is Zircuit?
  • What is Garfield?
  • What are the main features of Zircuit?​
  • What does it mean that Zircuit is EVM-compatible?
  • How do I join the Zircuit community as a member or builder?
  • Which wallets are supported?
  • What tech stack is Zircuit built on?
  • How does Zircuit work an a nutshell?​
  • How does Zircuit handle circuits differently than other L2s?
  • What does "security at the sequencer level" mean?
  • Does Zircuit have a token?

Frequently Asked Questions (FAQ)

PreviousIntroductionNextZircuit Token (ZRC)

Last updated 3 months ago

What is Zircuit?

Zircuit is an EVM-compatible zero-knowledge rollup powering the limitless potential of web3. Backed by pioneering L2 research, the network’s unique hybrid architecture combines battle-tested infrastructure with zero-knowledge proofs to give developers the best of both worlds. With cutting-edge performance and security at the sequencer level, users can explore new frontiers with faster transactions, reduced fees, and complete peace of mind.

What is Garfield?

Garfield is a version of the Zircuit network released in February 2025. The update brings support for TLOAD, TSTORE, MCOPY from Ethereum’s Cancun, is compatible with Ethereum’s Pectra uses optimized proving circuits, and removes the template proofs. Garfield comes with its own testnet, deprecating the legacy testnet.

What are the main features of Zircuit?​

Pioneering Research: Over the last year and a half, we’ve been at the forefront of research into topics like rollup security tooling, rollup compression, and scaling cryptography. This work has earned us multiple L2 research grants from the Ethereum Foundation.

Security at the Sequencer Level: Zircuit will protect users at the sequencer level by monitoring the mempool for malicious transactions and preventing their inclusion into a block. In comparison to typical security efforts that focus on the application and smart contract levels, Zircuit’s revolutionary approach goes directly to the underlying sequencer level.

Secure Native Bridge: Zircuit’s native bridge infrastructure incorporates best-in-class security architecture and safety practices. The canonical bridge is straightforward and easy to use while maximizing user security.

Cutting-Edge Performance: By decomposing circuits into specialized parts and aggregating proofs, Zircuit achieves greater efficiency and lower operating costs. Combined with larger transaction batches and accelerated proof processing, users benefit via faster and cheaper transactions.

Ethereum Application Compatibility: Zircuit works with all your favorite Ethereum apps. It supports all major wallets such as MetaMask, as well as tools like Hardhat. Deploy Ethereum dApps seamlessly without the need to learn a new programming language or framework.

What does it mean that Zircuit is EVM-compatible?

For the developers and users of our network, this means that tooling and wallets will work just as they are used to, resulting in minimal development overhead. Anyone can deploy Ethereum dApps seamlessly without the need to learn a new programming language or framework—simply change the deployment endpoints when you’re ready to go live. All gas fees on Zircuit are paid in ETH. Zircuit can deploy smart contract code that is compatible with the Ethereum Virtual Machine (EVM), which powers the Ethereum network itself.

How do I join the Zircuit community as a member or builder?

You can find us on or on .

Which wallets are supported?

Zircuit supports all major wallets such as MetaMask and Coinbase Wallet.

What tech stack is Zircuit built on?

Zircuit is composed of best-in-class technology improved by proprietary research efforts. The tech stack consists of:

  • Geth (Ethereum’s go client)

  • Halo2 (proof system)

  • code from the OP Stack (the battle tested framework for rollups)

How does Zircuit work an a nutshell?​

There are two actors involved in a rollup chain: Sequencer and User.

We maintain the account Merkle tree on-chain which can be updated by sending SNARK proofs. Users send transactions to the sequencer with signatures via RPC/APIs. The sequencer collects all the transactions and creates a batch which is processed by the SNARK circuit. If the circuit finds all transactions in the batch to be valid, it emits a proof. This validity proof will be submitted and verified on-chain which signifies that state was updated properly off-chain. This updates the on-chain account Merkle tree.

How does Zircuit handle circuits differently than other L2s?

Zircuit uses proprietary proof aggregation technology which separates circuits into fast parallel processes. This results in many smaller proofs which are faster to generate and which are later aggregated by Zircuit.

What does "security at the sequencer level" mean?

Zircuit services will constantly monitor the mempool for malicious transactions, exploit contracts, and more. Once detected and verified as malicious, Zircuit can prevent their inclusion into the next block. This means that every transaction on Zircuit will go through security checks resulting in a more secure chain for projects and end users.

Does Zircuit have a token?

Zircuit uses native ETH for gas. Zircuit also has a token, see details here:

Twitter/X
Discord
https://docs.zircuit.com/tokenomics/zircuit-token-zrc