RPC Providers

c8ntinuum publishes public endpoints for default application use and paid endpoints for higher-limit integrations. Public docs use c8ntinuum.com as the default mainnet RPC domain; c8ntinuum.io and c8ntinuum.link are also documented RPC domains. For chain IDs, currency metadata, explorers, and genesis resources, see Network Information - Mainnet Beta and Network Information - Testnet.

Mainnet endpoints

Surface	Default public endpoint	Alternate public endpoint	Paid endpoint
EVM JSON-RPC HTTP	`https://public-evm-rpc.c8ntinuum.com`	`https://public-evm-rpc.c8ntinuum.io`	`https://evm-rpc.c8ntinuum.io`
EVM JSON-RPC WebSocket	`wss://public-evm-rpc.c8ntinuum.com/websocket`	`wss://public-evm-rpc.c8ntinuum.io/websocket`	`wss://evm-rpc.c8ntinuum.io/websocket`
CometBFT RPC HTTP	`https://public-comet-rpc.c8ntinuum.com`	`https://public-comet-rpc.c8ntinuum.io`	`https://comet-rpc.c8ntinuum.io`
CometBFT RPC WebSocket	`wss://public-comet-rpc.c8ntinuum.com/websocket`	`wss://public-comet-rpc.c8ntinuum.io/websocket`	`wss://comet-rpc.c8ntinuum.io/websocket`
Cosmos gRPC	`-`	`public-comet-grpc.c8ntinuum.io:443`	`comet-grpc.c8ntinuum.io:443`
REST/LCD	`-`	`https://public-comet-grpc-web.c8ntinuum.io`	`https://comet-grpc-web.c8ntinuum.io`

Testnet endpoints

Surface	Public endpoint	Paid endpoint
EVM JSON-RPC HTTP	`https://public-testnet-evm.c8ntinuum.link`	`https://testnet-evm.c8ntinuum.link`
EVM JSON-RPC WebSocket	`wss://public-testnet-evm.c8ntinuum.link/websocket`	`wss://testnet-evm.c8ntinuum.link/websocket`
CometBFT RPC HTTP	`https://public-testnet-comet.c8ntinuum.link`	`https://testnet-comet.c8ntinuum.link`
CometBFT RPC WebSocket	`wss://public-testnet-comet.c8ntinuum.link/websocket`	`wss://testnet-comet.c8ntinuum.link/websocket`
Cosmos gRPC	`public-testnet-grpc.c8ntinuum.link:443`	`testnet-grpc.c8ntinuum.link:443`
REST/LCD	`https://public-testnet-grpc-web.c8ntinuum.link`	`https://testnet-grpc-web.c8ntinuum.link`

Paid endpoints require a valid API key through the X-API-Key header or an api_key query parameter. Header authentication is preferred.

Limits

The public and paid endpoints use the same protocol surfaces. They differ by authentication, request rate, and concurrent connection limits.

Tier/surface	Rate	Burst	Key
Free CometBFT	`25 r/s`	`50`	per visitor IP
Free EVM	`30 r/s`	`60`	per visitor IP
Free gRPC	`25 r/s`	`50`	per visitor IP
Free REST/LCD	`25 r/s`	`50`	per visitor IP
Paid surfaces	`300 r/s`	`600`	per API key
Paid per-IP safety cap	`500 r/s`	`500`	per visitor IP

Concurrent connection limits are 50 per IP for free HTTP/gRPC/REST surfaces, 1 per IP for free WebSockets, 200 per API key for paid EVM and CometBFT HTTP, 100 per API key for paid gRPC/REST, and 30 per API key for paid WebSockets. Requests over configured limits return HTTP 429.

EVM JSON-RPC request limits

Setting	Value
`eth_getLogs block range cap`	`10000 blocks`
`eth_getLogs result cap`	`10000 logs`
`EVM batch request limit`	`2000 requests`
`EVM batch response max size`	`50000000 bytes`
`EVM HTTP request body limit`	`2m`

Paginate long event scans by block range and persist cursors so retries do not duplicate work.

Using RPC Endpoints

ethers.js

import { JsonRpcProvider } from "ethers";
const provider = new JsonRpcProvider("https://public-evm-rpc.c8ntinuum.com");

viem

import { createPublicClient, http } from "viem";
const client = createPublicClient({
  transport: http("https://public-evm-rpc.c8ntinuum.com"),
});

Foundry

cast chain-id --rpc-url https://public-evm-rpc.c8ntinuum.com

Introduction

Developer Essentials

Tooling and Infrastructure

Reference

Guides

Resources

Mainnet endpoints

Testnet endpoints

Limits

EVM JSON-RPC request limits

Using RPC Endpoints

ethers.js

viem

Foundry

​Mainnet endpoints

​Testnet endpoints

​Limits

​EVM JSON-RPC request limits

​Using RPC Endpoints

​ethers.js

​viem

​Foundry

Mainnet endpoints

Testnet endpoints

Limits

EVM JSON-RPC request limits

Using RPC Endpoints

ethers.js

viem

Foundry