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
Powered by GitBook
On this page
  • Operators
  • Batcher
  • Proposer
  • Admin roles
  • Challenger
  • System Config Owner
  • L1 ProxyAdmin Owner
  • L2 ProxyAdmin Owner
  • Emergency roles
  • Guardian
  • Monitor
  • Operator
  1. Security

Privileged Roles

This page lists the EOAs that operate the Zircuit network.

Operators

Batcher

This is a hot wallet that continuously submits transactions onchain. It’s the component that submits new transaction batches and lets the L2 blockchain finalize new blocks.

  • Mainnet (Ethereum) address: 0xAF1E4f6a47af647F87C0Ec814d8032C4a4bFF145

  • Testnet (Sepolia) address: 0xa07FA473B87D7ADee161f458aF300255B65F33f6

Proposer

This is a hot wallet that continuously submits transactions onchain. It’s the component that submits new state roots for the L2 outputs that are essential for users to withdraw their funds on the L1.

  • Mainnet (Ethereum) address: 0xE8C20EA8eF100d7aa3846616E5D07A5aBb067C65

  • Testnet (Sepolia) address: 0x79B1a59c9d510213Dce55C106fcBc64D2F98f34E

Admin roles

Challenger

This is a testnet role that is authorized to call deleteL2Outputs() to remove a state commitment. This is temporary and for emergency purposes only. On mainnet, this role will not exist, as state roots will not be reset.

System Config Owner

This is the address authorized to change the settings in the SystemConfig contract. These settings are:

  • The blocks signer: L2 blocks propagated among Zircuit nodes via peer-to-peer communication must be signed by this wallet to be considered valid.

  • The batcher hash: identifier for the batcher operator.

  • The gas config: overhead and scalar values used to determine the L1 costs.

  • The gas limit: the maximum amount of gas allowed in every L2 block.

  • The resource config: the configuration for the EIP-1559 based curve for the deposit gas market.

L1 ProxyAdmin Owner

This is the owner of the ProxyAdmin contract deployed on the L1 that controls most of the L1 contracts and can upgrade them if necessary. The ProxyAdmin contract is an auxiliary contract meant to be assigned as the admin of an ERC1967 Proxy, based on the OpenZeppelin implementation.

L2 ProxyAdmin Owner

This is the owner of the ProxyAdmin contract deployed on the L2 that controls most of the L2 contracts and can upgrade them if necessary. The ProxyAdmin contract is an auxiliary contract meant to be assigned as the admin of an ERC1967 Proxy, based on the OpenZeppelin implementation.

Emergency roles

Guardian

The OptimismPortal is pausable as a backup safety mechanism that allows a specific GUARDIAN address to temporarily halt deposits and withdrawals to mitigate security issues if necessary.

Monitor

Addresses with the MONITOR role can pause message passing from L1 to L2, which includes ERC20, ERC721 and ETH deposits and withdrawals. Similarly on L2, this role can also pause message passing from L2 to L1.

Operator

Addresses with the OPERATOR role have all the capabilities of the MONITOR role, and additionally they can unpause message passing, reenabling bridging. This role can also throttle the amount of ETH that is allowed to be deposited from L1 to L2 and similarly the amount of ETH that can be withdrawn from L2 to L1.

PreviousSecurityNextBug Bounty

Last updated 7 months ago