EVM chains
Corvus BSC and Polygon endpoints: standard EVM JSON-RPC and WebSocket, one metro each, included with your rental.
Beside the Solana fleet we run one BSC node and one Polygon node. Both speak standard EVM JSON-RPC, so whatever client you already use works unchanged; point it at the endpoint and go.
| Chain | Chain ID | Metro | HTTP JSON-RPC | WebSocket |
|---|---|---|---|---|
| BSC | 56 | Frankfurt | http://bsc.fra.corvus-labs.io:8545 | ws://bsc.fra.corvus-labs.io:8546 |
| Polygon | 137 | Amsterdam | http://poly.ams.corvus-labs.io:8545 | ws://poly.ams.corvus-labs.io:8546 |
Each chain runs in the one metro listed.
Get access
Both chains are included with your rental at no extra cost, but the allowlist for them is handled by hand rather than in the dashboard. Ask us on Discord with the public egress IP your client calls from, and we'll add it.
That is the same kind of IP allowlist the Solana endpoints use (Access & authentication), so register the address traffic actually leaves from rather than the one your host thinks it has.
curl -s -X POST http://bsc.fra.corvus-labs.io:8545 \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'What runs where
These are plain EVM RPC nodes, and JSON-RPC over HTTP and WebSocket is the whole surface. Everything else Corvus sells is Solana only: Falcon, aRPC, Shredstream and Yellowstone gRPC have no BSC or Polygon equivalent.
If you need EVM capacity in another region, or a dedicated node, ask us on Discord rather than assuming an endpoint is there.
Shredstream
Receive raw Solana shreds over push-based UDP from Corvus Shredstream: registration, firewall rules, and how to verify packets arrive.
Corvus Solana validator
Verify the Corvus Solana validator vote account on a live explorer before delegating SOL, then choose native staking or corvusSOL liquid staking.