ZetaChain RPC Endpoint

Flat-rate ZetaChain RPC provider and ZetaChain RPC node access: free tier, no KYC, HTTP & WebSocket. ZetaChain mainnet chain ID 7000.

ZetaChain mainnet RPC URL: https://rpc.swiftnodes.io/rpc/zetachain?key=YOUR_API_KEY
WebSocket: wss://rpc.swiftnodes.io/ws/zetachain?key=YOUR_API_KEY

ZetaChain is a Cosmos-SDK Layer 1 with an EVM (ZetaEVM) designed for omnichain smart contracts that can read from and write to connected chains, including non-smart-contract chains like Bitcoin, without wrapped assets. SwiftNodes provides ZetaChain mainnet RPC over HTTP and WebSocket.

Network: ZetaChain
Type: EVM
Chain ID: 7000
Slug: zetachain
Native token: ZETA (Zeta)
Block time: ~5 seconds
Finality: Instant (single-slot BFT finality)
Mainnet: February 1, 2024
Category: Layer 1 (Cosmos SDK, omnichain)

ZetaChain on the SwiftNodes fleet, right now

Status: online
Latency: 57 ms
Latest block: 19,367,936
WebSocket: available

8 of 12 probed RPC methods supported (archive, batch, debug_traceCall, eth_getProof). The gaps are listed per chain 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

ZetaChain developer facts, measured

Block time:
~3.82 s (average of the last 1,000 blocks)
Finality:
the latest block is already reported as finalized
eth_getLogs range:
5,000-block ranges accepted; the next size we test was refused
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 ZetaChain

ZetaChain launched its mainnet on February 1, 2024. It runs on CometBFT (Tendermint) consensus with validators voting in proportion to staked ZETA, giving roughly 5-second block times and instant, non-reversible finality.

ZetaChain's defining feature is cross-chain interoperability managed by a distributed TSS (threshold signature scheme) validator set, allowing contracts to control native assets on external chains rather than relying on centralized bridges. Developers deploy standard Solidity contracts on the EVM and use Hardhat, Foundry, and ethers.js.

Common Use Cases on ZetaChain

  • Omnichain smart contracts
  • Native Bitcoin DeFi without wrapped BTC
  • Cross-chain swaps and messaging
  • Bridgeless asset transfers
  • Multi-chain liquidity routing

ZetaChain Ecosystem

Hosts omnichain applications and integrations including ZetaSwap, and works with cross-chain tooling; the network connects to Ethereum, BNB Chain, Polygon, and Bitcoin.

ZetaChain Mainnet RPC URL (HTTP)

https://rpc.swiftnodes.io/rpc/zetachain?key=YOUR_API_KEY

ZetaChain WebSocket RPC URL

wss://rpc.swiftnodes.io/ws/zetachain?key=YOUR_API_KEY

Quick Start: Connect to ZetaChain

cURL

curl -X POST https://rpc.swiftnodes.io/rpc/zetachain?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/zetachain?key=YOUR_API_KEY"
);

const blockNumber = await provider.getBlockNumber();
console.log("ZetaChain block:", blockNumber);

viem

import { createPublicClient, http } from "viem";

const client = createPublicClient({
  transport: http("https://rpc.swiftnodes.io/rpc/zetachain?key=YOUR_API_KEY"),
});

const blockNumber = await client.getBlockNumber();

web3.py

from web3 import Web3

w3 = Web3(Web3.HTTPProvider("https://rpc.swiftnodes.io/rpc/zetachain?key=YOUR_API_KEY"))
print("ZetaChain block:", w3.eth.block_number)

Add ZetaChain to MetaMask

Network Name: ZetaChain (SwiftNodes)
RPC URL: https://rpc.swiftnodes.io/rpc/zetachain?key=YOUR_API_KEY
Chain ID: 7000
Currency Symbol: ZETA
WebSocket: wss://rpc.swiftnodes.io/ws/zetachain?key=YOUR_API_KEY

Bridging to ZetaChain

ZetaChain's protocol-level TSS handles native deposits and withdrawals to connected chains; assets move in and out without third-party wrapped-token bridges.

Features of SwiftNodes for ZetaChain

  • 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 ZetaChain

Rate Limits

PlanPriceHTTP req/sWS msg/s
Free$0/mo21
Starter$49/mo5025
Growth$89/mo15075
Scale$149/mo300150
Pro$249/mo500250

Frequently Asked Questions: ZetaChain

What's ZetaChain's chain ID?

ZetaChain mainnet is chain ID 7000.

Does ZetaChain support native Bitcoin?

Yes - ZetaChain's TSS validator set can custody and move native BTC, enabling Bitcoin DeFi without wrapped tokens.

Is ZetaChain EVM-compatible?

Yes - ZetaChain runs ZetaEVM, so standard Solidity contracts and Ethereum tooling work directly.

Is WebSocket supported?

Yes - SwiftNodes provides HTTP and WebSocket (wss://) endpoints with eth_subscribe support.

ZetaChain 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.
  • ZetaChain RPC: One Contract That Touches Native BitcoinZetaChain is an omnichain L1 (chain ID 7000) where a single Solidity contract can read and write across connected chains — including native Bitcoin, no wrapping, no centralized bridge. The ZetaEVM is standard eth_* (viem/ethers work), but it sits on a Cosmos-SDK base with a TSS validator set. Here's the developer map.

Related L2 & rollup chains

Explore RPC endpoints for other L2 & rollup networks on SwiftNodes:

Ready to start building on ZetaChain? Connect your wallet and get a free API key in 30 seconds. No email or KYC required.