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
  • Unsupported Opcodes
  • Cancun opcodes
  • Other
  • Limitations
  1. Garfield Testnet

Differences & Limitations

This page lists the opcodes that are not fully supported by Zircuit networks at this time.

PreviousFaucetNextContract Addresses

Last updated 2 months ago

This page is for the Zircuit Garfield Testnet.

Unsupported Opcodes

Cancun opcodes

A hash of the blob’s KZG commitment. Since blobs themselves are not stored on the execution layer, this is used to validate a blob belonging to a transaction. If the blob data is altered in any way, its hash will change as well, so the actual hash found on-chain will no longer match.

Provides the blob base fee for the current block. This opcode helps with accounting for blob data usage costs, similar to the existing opcode BASEFEE.

Other

SELFDESTRUCT

Zircuit's Garfield networks do not support SELFDESTRUCT in any form. The opcode is handled the same as the INVALID opcode.

PREVRANDAO/DIFFICULTY

The opcode PREVRANDAO returns the mixHash field of the block. However, it will always be 0.

Limitations

Precompile and Opcode Limits

The circuits used by Zircuit Garfield currently restrict the number of calls possible to precompiles. Transactions that exceed these limits will be dropped.

Precompile or Opcode
Limit

keccak256

3157

ecRecover

119

modexp

23

ecAdd

50

ecMul

50

ecPairing

2

BLOBHASH
BLOBBASEFEE