Overview

c8ntinuum exposes an Ethereum-compatible JSON-RPC endpoint at https://public-evm-rpc.c8ntinuum.com. The default public EVM namespace allowlist is eth,net,web3. Archive or private node profiles may enable additional namespaces such as debug or txpool, but applications should not assume those namespaces are available on the default public endpoint.

Supported Namespaces

The local development node started by local_node.sh enables eth,txpool,personal,net,debug,web3.

Commonly Used Methods

For concrete block, transaction, receipt, log, broadcast, CometBFT, and REST/LCD examples, see Node Interface Calls.

Method availability matrix

Endpoint Configuration

Mainnet endpoints use three TLDs: c8ntinuum.com for the default public free RPCs, and c8ntinuum.io for alternate public and paid RPCs. c8ntinuum.link serves mainnet too, with the same host names as c8ntinuum.io (for example https://public-evm-rpc.c8ntinuum.link, and the paid https://evm-rpc.c8ntinuum.link). Testnet endpoints live on c8ntinuum.link only and have testnet in the hostname. For the canonical free / alternate / paid matrix and rate limits, see RPC Providers.
Paid endpoints require a valid API key through X-API-Key or ?api_key=. To get one, email [email protected]; a dedicated self-service dashboard is planned.

Request policy

EVM JSON-RPC HTTP accepts POST / with Content-Type: application/json. OPTIONS is allowed for preflight compatibility. GET /, non-JSON POST /, and unsupported paths are rejected by the RPC proxy.

Example Request