Celo RPC Endpoint

Celo runs stablecoin payments for real users on one-second blocks. Get a dedicated endpoint with full archive access and debug methods included.

chain id · 42220JSON-RPC 2.0WebSocketFull archiveDebug
LIVE LATENCY
19ms
LIVE
gateway round-trip · sampled every second
IN PRODUCTION ATChainlinkEnjinTiingoGains Network

Your endpoint, ready in one line.

Drop this URL into your RPC client, HTTP library or wallet config. No SDK install required.

HTTPS
https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/celo
WEBSOCKET
wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/celo

Replace YOUR_API_KEY with your API key. Get a free key →

Pick your stack.

Copy-paste examples for the libraries you already use. Swap the API key, hit run.

import { ethers } from "ethers";

const provider = new ethers.JsonRpcProvider(
  "https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/celo"
);

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

Connect your dApp, bot, or protocol to Celo Mainnet with BoltRPC. Celo is the payments-focused chain that migrated from standalone L1 to an Ethereum Layer 2, and predictable request-unit pricing keeps your RPC costs as boring as your users expect their payments to be.

Chain at a Glance

Chain ID42220
ProtocolOptimistic rollup on the OP Stack (migrated from L1 in 2025)
Block time~1 second
Gas tokenCELO (fees also payable in stablecoins via fee abstraction)
SettlementEthereum mainnet
EVM compatibleYes

What Celo is Built For

Celo is one of the few chains whose traffic is dominated by real-world payments rather than trading. Its ecosystem centers on stablecoins, cUSD, cEUR and bridged dollars, moving between mobile wallets, with fee abstraction that lets users pay gas in the stablecoin they are sending. In 2025 Celo completed its migration from a standalone L1 to an Ethereum Layer 2 on the OP Stack, keeping its one-second blocks and sub-cent fees while inheriting Ethereum settlement. For developers that means standard EVM tooling, ethers.js, viem, Foundry, Hardhat, against a chain where uptime directly affects whether someone’s remittance arrives. Payment backends poll balances and confirmations continuously, a workload where rate-limited public endpoints show up as support tickets.

Common Use Cases on Celo

Stablecoin payments and remittances Payment apps confirm transfers in near real time. Their backends poll eth_getTransactionReceipt and stream Transfer events continuously, sustained read traffic that scales with users, not with trading volume.

Deposit detection for wallets and merchants Merchant tools and custodial wallets watch addresses for incoming stablecoins. An eth_getLogs pipeline over one-second blocks needs a provider that sustains continuous read load without gaps.

Accounting, compliance and history Balance-at-date reports and transaction history exports are archive workloads. Full archive access on the standard endpoint means no second provider for historical queries.

DeFi on payment rails Lending and FX between Celo stablecoins run the classic DeFi read pattern: continuous eth_call polling against rates and positions, with WebSocket streams for liquidations.

Built for teams that ship on Celo.

Full archive access included

BoltRPC serves Celo with full historical state, measured live against our own nodes. Query any balance or contract state at any block, transaction history features, accounting exports and compliance reporting work without a separate archive provider.

Built for payment backends

Wallets and payment processors confirm transfers by polling receipts and balances on every user action. One-second blocks make that a high-frequency workload; a dedicated endpoint keeps confirmation latency flat when your user count grows.

Debug methods included

debug_* methods are available on Celo for tracing failed transactions and inspecting execution, useful when a stablecoin transfer with fee abstraction behaves unexpectedly.

WebSocket streaming included

Subscribe to new blocks and transfer events over WebSocket at no extra charge. Payment services credit deposits the moment they land instead of discovering them a polling interval later.

L2 migration handled for you

Celo's move to the OP Stack changed the node software under every RPC provider. BoltRPC's operator tracks upgrades and hard forks for every supported chain, so your integration survives network transitions without code changes.

Full JSON-RPC coverage.

Every standard Celo method you would expect. Archive-only methods are available on request for qualifying plans.

STANDARD5
eth_calleth_getLogseth_sendRawTransactioneth_getTransactionReceipteth_getBalance
ARCHIVEON REQUEST3
eth_getBalanceeth_calldebug_traceTransaction

Celo, explained.

Common questions about connecting to Celo over BoltRPC.

Ship on Celo this week.

An API key in under 60 seconds, Celo plus 34 other chains, and a team that answers when you write.