Taiko RPC Endpoint
Flat-rate Taiko RPC provider and Taiko RPC node access: free tier, no KYC, HTTP & WebSocket. Taiko mainnet chain ID 167000.
https://rpc.swiftnodes.io/rpc/taiko?key=YOUR_API_KEYwss://rpc.swiftnodes.io/ws/taiko?key=YOUR_API_KEYTaiko is a Type-1 zk-rollup — the most Ethereum-equivalent of the zkEVMs. Every Ethereum block can theoretically be re-executed on Taiko's prover, and contracts deploy bit-identically. Taiko emphasizes decentralization: anyone can propose blocks (based rollup) and anyone can prove them.
taikoTaiko on the SwiftNodes fleet, right now
12 of 12 probed RPC methods supported (archive, batch, debug_traceCall, trace_transaction). Full results in the method support matrix.
Status and latency from our health checks, refreshed about every 5 minutes. Uptime history. Method support probed automatically on 2026-10-04. Network status
Taiko developer facts, measured
- Block time:
- ~2 s (average of the last 1,000 blocks)
- Finality:
- the finalized tag trails the head by ~486 blocks (~16 min)
- eth_getLogs range:
- 50,000-block ranges accepted (the largest we test)
- Historical state:
- readable at least 1,000,000 blocks back
Measured 2026-10-04 through this page's endpoint, re-measured weekly. Limits can differ between the upstream nodes behind it. All chains: measured chain facts.
About Taiko
Taiko launched mainnet (Alethia) in May 2024 after years of testnet iteration. The chain pursues Type-1 zkEVM equivalence — exact Ethereum opcode behavior — at the cost of slower proof generation than less-equivalent designs.
Taiko is a "based rollup": block proposing happens via Ethereum L1 itself, meaning L1 validators include Taiko blocks as part of normal Ethereum block production. This removes the need for a Taiko-specific sequencer and inherits Ethereum's liveness and censorship resistance.
Common Use Cases on Taiko
- Ethereum-equivalent dApp deployment with no code changes
- Decentralized rollup applications (no sequencer trust)
- ZK-research applications leveraging Type-1 equivalence
- Anti-MEV applications via based-sequencing model
- Standard DeFi with stronger decentralization guarantees
Taiko Ecosystem
Early ecosystem; existing Ethereum protocols can deploy unchanged. Native projects include Taiko's own bridge and developer tools. Growing slowly with emphasis on decentralization over incentive-driven TVL.
Taiko Mainnet RPC URL (HTTP)
https://rpc.swiftnodes.io/rpc/taiko?key=YOUR_API_KEYTaiko WebSocket RPC URL
wss://rpc.swiftnodes.io/ws/taiko?key=YOUR_API_KEYQuick Start: Connect to Taiko
cURL
curl -X POST https://rpc.swiftnodes.io/rpc/taiko?key=YOUR_API_KEY \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'ethers.js
import { JsonRpcProvider } from "ethers";
const provider = new JsonRpcProvider(
"https://rpc.swiftnodes.io/rpc/taiko?key=YOUR_API_KEY"
);
const blockNumber = await provider.getBlockNumber();
console.log("Taiko block:", blockNumber);viem
import { createPublicClient, http } from "viem";
const client = createPublicClient({
transport: http("https://rpc.swiftnodes.io/rpc/taiko?key=YOUR_API_KEY"),
});
const blockNumber = await client.getBlockNumber();web3.py
from web3 import Web3
w3 = Web3(Web3.HTTPProvider("https://rpc.swiftnodes.io/rpc/taiko?key=YOUR_API_KEY"))
print("Taiko block:", w3.eth.block_number)Add Taiko to MetaMask
https://rpc.swiftnodes.io/rpc/taiko?key=YOUR_API_KEYwss://rpc.swiftnodes.io/ws/taiko?key=YOUR_API_KEYBridging to Taiko
Taiko Bridge (https://bridge.taiko.xyz) for canonical Ethereum ↔ Taiko. Across and other fast bridges for alternative routes.
Features of SwiftNodes for Taiko
- Load-balanced across multiple upstream nodes wherever a chain has more than one, with automatic failover
- Health-checked every 2 minutes with automatic failover
- Free tier available — no credit card or KYC required
- Flat-rate monthly pricing with no per-request fees
- HTTP and WebSocket support
- One API key works across all 75+ supported chains, including Taiko
Rate Limits
| Plan | Price | HTTP req/s | WS msg/s |
|---|---|---|---|
| Free | $0/mo | 2 | 1 |
| Starter | $49/mo | 50 | 25 |
| Growth | $89/mo | 150 | 75 |
| Scale | $149/mo | 300 | 150 |
| Pro | $249/mo | 500 | 250 |
Frequently Asked Questions: Taiko
What's Taiko's chain ID?
Taiko Alethia (mainnet) is chain ID 167000. Hekla testnet is 167009.
What's a based rollup?
A rollup where block proposing happens through L1 (Ethereum) itself — no dedicated rollup sequencer. Ethereum validators propose Taiko blocks as part of normal Ethereum block production.
Why is Taiko's proof time longer than other zkEVMs?
Type-1 zkEVM equivalence means every Ethereum opcode is proven exactly — this is more expensive than language-equivalent zkEVMs that simplify some opcodes. Proof times are decreasing as proving systems improve.
Taiko guides from the blog
- Which Chains Stopped? 43 Days of Block Timestamps Across 110 ChainsBetween August 25 and October 6, 2026, ten of 110 chains we scanned stopped producing blocks for 10 minutes or more. TAC was down 10.6 days, Neutron 77.75 hours, Cosmos Hub 24.8 hours, Cronos 17 hours. The full list, the method, and the raw data.
- Taiko RPC: The L2 With No SequencerTaiko is a based rollup — Ethereum's own validators propose its blocks, so there's no sequencer to trust or to go down. It's also a Type-1 zkEVM, so your Ethereum tooling works bit-identically. Chain ID 167000, ETH gas, ~12s blocks. Here's what 'based' and 'Type-1' actually change for a developer.
Related L2 & rollup chains
Explore RPC endpoints for other L2 & rollup networks on SwiftNodes:
Ready to start building on Taiko? Connect your wallet and get a free API key in 30 seconds. No email or KYC required.