Celo RPC Endpoint

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

Celo is a mobile-first network that migrated from a standalone Layer 1 to an Ethereum Layer 2 in March 2025, built on the OP Stack with EigenDA for data availability. SwiftNodes provides Celo mainnet RPC over HTTP and WebSocket.

About Celo

Celo originally launched as a Layer 1 in 2020 and completed its transition to an Ethereum Layer 2 at block 31,056,500 on March 26, 2025, using Optimism's OP Stack and EigenDA. Block times decreased from about 5 seconds to roughly 1 second after the migration.

Celo keeps chain ID 42220, and CELO remains the native gas token with ERC-20-style token duality. The network focuses on mobile-friendly payments and stablecoins (such as cUSD), and developers use standard Solidity contracts and Ethereum tooling.

Common Use Cases on Celo

• Mobile-first payments
• Stablecoin transfers (cUSD, cEUR)
• DeFi protocols
• Regenerative finance (ReFi)
• Real-world asset and impact projects

Celo Ecosystem

Hosts mobile-focused DeFi and stablecoin apps including Mento (cUSD/cEUR), Ubeswap, and a range of ReFi projects; native stablecoins are central to the ecosystem.

Celo Mainnet RPC URL (HTTP)

Celo WebSocket RPC URL

Quick Start: Connect to Celo

cURL

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

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

viem

import { createPublicClient, http } from "viem";

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

const blockNumber = await client.getBlockNumber();

web3.py

from web3 import Web3

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

Add Celo to MetaMask

Bridging to Celo

Following the L2 migration, Celo supports native bridging to Ethereum via the OP Stack; third-party bridges such as Wormhole and Squid/Axelar connect it to other chains.

Features of SwiftNodes for Celo

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

Rate Limits

Frequently Asked Questions: Celo

Celo RPC methods

Measured weekly through this endpoint: what each method returns on Celo, its limits, and an example request.

• eth_getLogssupported
• eth_getBlockReceiptssupported
• eth_feeHistorysupported
• eth_getProofsupported
• eth_createAccessListsupported
• debug_traceCallsupported
• trace_blocksupported
• trace_transactionnot available

Celo guides from the blog

• Celo RPC: The L2 Where You Pay Gas in StablecoinsCelo became an OP Stack L2 in March 2025 (with EigenDA), keeping chain ID 42220. It's standard EVM, so viem/ethers work — but it has a feature almost no other chain does: pay transaction fees in stablecoins like cUSD, not just the native token. Here's the developer map, including fee currencies and the L1→L2 shift.

Related EVM chains

Explore RPC endpoints for other EVM networks on SwiftNodes: