Solana

The Solana Gateway provides SVM JSON-RPC over HTTP for account, block, and transaction state. Its gas token is SOL.

Supported networks

Solana does not use an EVM Chain ID. Copy the complete Access Point from the dashboard.

Endpoint-free calls

On an Accelerator hit, these methods work without an Endpoint:

• getSlot with omitted parameters, [], or finalized commitment;
• getLatestBlockhash with omitted parameters, [], or finalized commitment;
• getBlock with an explicit slot plus finalized, rewards: false, and a supported transaction-version configuration.

See Accelerator for exact parameter forms and cache limitations.

Configure complete method access

Provider sync does not currently cover Solana:

1. Create a Gateway for the target Solana network.
2. Manually add a JSON-RPC Solana Endpoint on the same network.
3. Add the Endpoint to the default JSON-RPC route and complete its health check.
4. Call getHealth to verify availability, then use getGenesisHash or application data to confirm the network.

curl '<solana_access_point>' \
  -H 'Authorization: Bearer <app_api_key>' \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"getHealth","params":[]}'

A healthy node normally returns {"result":"ok"}.

getHealth is not an Accelerator method, so this verification requires a usable Endpoint.

Current limits

• Single Solana JSON-RPC calls over HTTP are supported; batch, WebSocket subscriptions, and public gRPC are not.
• Solana Yellowstone gRPC and vendor-specific REST endpoints are not exposed.
• Commitment levels, history range, transaction versions, and archive data depend on the upstream Endpoint.
• Mainnet Beta and Devnet use independent routes and never fail over across networks.

See JSON-RPC and Errors and troubleshooting for shared behavior.