Zircuit is a zk-rollup built on OP-Stack-derived infrastructure with one distinctive feature: the sequencer screens every transaction before inclusion. Flagged transactions are quarantined rather than executed — a protocol-level security layer that most rollups don't have. Few independent RPC providers serve Zircuit. NodeFlare runs a dedicated node, so you can start building in under a minute.
Zircuit RPC URLs
Public endpoint — no API key:
https://rpc.nodeflare.app/zircuit/publicKeyed endpoint (free account — higher limits, heavy methods):
https://rpc.nodeflare.app/zircuit/v1/{YOUR_KEY}Get your free key → — no credit card.
Quick start
curl https://rpc.nodeflare.app/zircuit/public \
-X POST \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'import { ethers } from 'ethers';
const provider = new ethers.JsonRpcProvider(
'https://rpc.nodeflare.app/zircuit/public'
);
console.log('Zircuit block:', await provider.getBlockNumber());Zircuit at a glance
| Parameter | Value |
|---|---|
| Chain ID | 48900 (0xbf04) |
| Currency | ETH |
| Type | zk-rollup (OP-Stack infrastructure) |
| Block time | ~2 s |
| Finality | Soft ~2 s · Hard on zk-proof to L1 |
| Explorer | explorer.zircuit.com |
On sequencer quarantine: Zircuit's sequencer validates transactions against known attack patterns before inclusion. If a transaction gets stuck with no obvious gas or nonce reason, it may have been quarantined — a security hold at the protocol level, not a standard revert. This is intentional behavior, not a bug.
Zircuit launched in 2024 and its DeFi ecosystem is still in early growth. That's actually an advantage for indexers and developers: full-history eth_getLogs scans across the entire chain are feasible today in a way they'll never be once the chain matures.
Free tier
- 2,000,000 compute units/month — no credit card
eth_getLogs(75 CU),trace_*/debug_*(100 CU) included on free- Every supported chain under one key — Zircuit, Ethereum, Base, Arbitrum, and more
- Multi-region routing with automatic failover
Add Zircuit to MetaMask
| Field | Value |
|---|---|
| Network name | Zircuit |
| RPC URL | https://rpc.nodeflare.app/zircuit/public |
| Chain ID | 48900 |
| Currency symbol | ETH |
| Block explorer | https://explorer.zircuit.com |
FAQ
What is the Zircuit RPC URL?
https://rpc.nodeflare.app/zircuit/public — no API key required, rate-limited per IP. A free key unlocks higher limits and heavy methods (eth_getLogs, trace_*, debug_*).
Is the Zircuit RPC free? Yes. The public endpoint is free without sign-up; a free account adds 2M CU/month and a dedicated keyed path.
Does eth_getLogs work on Zircuit? Yes — with a free API key. Zircuit's DeFi ecosystem is still early, so full-history scans are practical; each call costs 75 CU against your monthly quota.
What is Zircuit's sequencer security screening? Zircuit's sequencer checks incoming transactions against known exploit patterns before including them in a block. Transactions that match are quarantined rather than executed — they're held, not reverted. Regular dApp transactions are unaffected; the feature primarily targets MEV attacks and known exploit signatures.
Does Zircuit support WebSocket?
Zircuit WebSocket support is on the roadmap. For now, use the HTTPS endpoint above; poll with eth_blockNumber for lightweight head-tracking.
Building on Zircuit? Get your free NodeFlare key → — covers Zircuit plus every supported chain.