Skip to main content

Networks and RPC endpoints

Use the local devnet for a working connection today. The shared-network development configuration uses chain IDs 56580 for testnet and 5658 for mainnet. The public hosts below are proposals; DNS, TLS and live availability are unverified.

Local devnet

Available locally

Start the cpp-node devnet first. Development funds have no value.

Chain ID
31337 (0x7a69)
Currency
JOLT · 18 decimals
HTTP RPC
http://127.0.0.1:30400
WebSocket RPC
ws://127.0.0.1:30400
Explorer
Use a locally configured indexer
Faucet
Funded development accounts
Try a local request
curl http://127.0.0.1:30400 \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'

Local devnet​

Start it with the quickstart. HTTP and WebSocket share port 30400 by default. The currency is JOLT with 18 decimals, and chain ID 31337 identifies the disposable development network. Genesis provides funded development accounts; there is no need for a public faucet.

Proposed testnet​

Proposed HTTP: https://rpc.testnet.joltzu.com. Proposed WebSocket: wss://rpc.testnet.joltzu.com. The proposed explorer and faucet hosts are directory placeholders, not confirmed services.

After an actual deployment, publish the supported methods, credential policy, wallet compatibility, CORS, rate limits, history floors and faucet rules. Neither the hostname nor the configured chain ID proves a canonical network identity. Verify launch information and the trusted genesis/checkpoint too.

Proposed mainnet​

Proposed HTTP: https://rpc.joltzu.com. Proposed WebSocket: wss://rpc.joltzu.com. There is no mainnet faucet. This directory does not announce mainnet launch or confirm an explorer.

Envio and The Graph​

Joltzu-hosted Envio HyperIndex and The Graph query APIs are planned for both testnet and mainnet. Their URLs are TBD. See indexing endpoints for the service directory and a GraphQL request template.

Public RPC versus local RPC​

The current gateway requires a bearer credential and exact method allowlists. The node's shared-network configuration allows 32 Ethereum methods per client and no joltzu_* methods, so native proofs, energy reads and native submission are not reachable through that profile. This is deployment configuration, not a live endpoint. Ordinary wallets cannot attach that credential to their RPC URL. Public anonymous or wallet-compatible endpoints require an explicit deployment policy. These templates do not assume one exists.

Use POST / for HTTP. With an authenticated deployment, add its required authorization header. WebSocket URLs alone do not establish that a browser may open an authenticated session.

Download the local read-only RPC examples for an HTTP client. They target your own running devnet.