SolidRPC plans change on 28th October. Some prices are going up. Lock in today’s pricing and limits by activating before then. See what’s changing.
Skip to main content
RPC operator referenceHTTPS / WSS · JSON-RPC 2.0

Viction RPC endpoint

Viction (chain ID 88) is served over HTTPS POST JSON-RPC 2.0. Full and archive nodes back the endpoint, supporting standard EVM methods, historical state, debug_* methods. Free, paid plans, and PAYG include Viction.

Network information

NetworkViction
Chain ID88
Endpointhttps://rpc.solidrpc.io/YOUR_API_KEY/evm/88
AccessFree and paid
TypeMainnet · L1
Native currencyVIC
Node typesFull + Archive
Methodsstandard, debug
ProtocolHTTPS JSON-RPC 2.0. WebSocket unavailable. WebSocket details

Quickstart

Fetch the latest Viction block number. Replace YOUR_API_KEY with a key from the dashboard. New accounts start on the Free plan, no card required (see getting started):

Request example
curl https://rpc.solidrpc.io/YOUR_API_KEY/evm/88 \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Archive access and tracing

There is no separate archive endpoint for Viction. Historical queries route to archive nodes automatically by block age, at no surcharge.

The debug_* tracing namespace is available:

Request example
curl https://rpc.solidrpc.io/YOUR_API_KEY/evm/88 \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"debug_traceTransaction","params":["0xTRANSACTION_HASH",{"tracer":"callTracer"}],"id":1}'

Parity-style trace_* methods are not available on this chain. Use debug_traceTransaction and debug_traceBlockByNumber instead.

Details on archive nodes and tracing.

Limits and errors

Quotas and rate limits are account-wide, not per-chain. Method calls to Viction draw from the same response-unit quota and rate limit as every other network. Error bodies are identical everywhere. See the error reference.