c8ntinuum publishes a public EVM WebSocket endpoint at: 
wss://public-evm-rpc.c8ntinuum.com/websocket
The documented mainnet alternate is wss://public-evm-rpc.c8ntinuum.io/websocket, and the testnet endpoint is wss://public-testnet-evm.c8ntinuum.link/websocket. Applications can use WebSocket connections for subscription-style workflows, while operators running their own infrastructure should plan for connection limits, reconnection behavior, and monitoring.

​
Application guidance

NeedSuggested approach
New block notificationsUse WebSocket subscriptions where supported by your client library.
Contract eventsSubscribe for live events and backfill with bounded eth_getLogs queries.
Long historical scansPrefer an indexer over an unbounded RPC or WebSocket workload.

​
Operator checklist

  • Define public versus private WebSocket exposure.
  • Monitor active connections and reconnect storms.
  • Apply the documented connection limits: free WebSockets allow 1 connection per IP, while paid WebSockets allow 30 connections per API key.
  • Keep historical backfills on HTTP RPC or indexer infrastructure instead of long-lived subscription paths.
For standard RPC methods, see JSON-RPC API.