ws://localhost:4000/ws/rpc/ethereum for the included public profile. For a named profile, use /ws/rpc/profile/my-app/ethereum. Explicit strategy routes include /ws/rpc/fastest/ethereum, /ws/rpc/load-balanced/ethereum, and /ws/rpc/latency-weighted/ethereum.
eth_subscription notifications contain real block headers; an open socket alone does not prove subscription delivery.
To stop a subscription, send eth_unsubscribe with the returned ID as its only parameter. Subscription ownership belongs to the downstream connection.
Provider configuration
A connected upstream WebSocket is required. In RPC Core v0.5.0,subscribe_new_heads: true enables both automatic block tracking and client newHeads eligibility. New profiles sharing an existing connection work after successful reload. See Provider configuration.
Supported streams and recovery
The released subset includesnewHeads and logs, not pending transactions.
Recovery after a provider failure is bounded and can terminate the connection
explicitly; WebSocket subscriptions defines
it and what your application must checkpoint.
WebSocket batching is not part of the advertised interface. Ordinary RPC execution still follows the method safety contract.
For a public deployment, terminate TLS to provide wss:// and protect the endpoint through your network or reverse proxy. Core does not authenticate clients.