Solana infrastructure, included with every server. LEARN MORE>

OpenInfra.shopeninfra.sh

Migrating from QuickNode

Move standard Solana RPC and PubSub traffic by changing the endpoint and API-key placement.

Compatibility boundary

  • Standard Solana JSON-RPC method names and payload shapes remain the same.
  • Standard Solana WebSocket subscription methods remain the same.
  • QuickNode add-ons and provider-specific APIs require separate replacements.
  • Your active OpenInfra gateway plan determines rate limits.

  1. Update environment variables

    Before:

    QN_ENDPOINT=https://example-endpoint.solana-mainnet.quiknode.pro/your_token/

    After:

    OPENINFRA_RPC_URL=https://rpc.sol.openinfra.shOPENINFRA_API_KEY=sk_live_xxxxxxxxxxxx

  2. Update the RPC client

    -const conn = new Connection(process.env.QN_ENDPOINT!);+const conn = new Connection(process.env.OPENINFRA_RPC_URL!, {+  commitment: "confirmed",+  httpHeaders: { "x-api-key": process.env.OPENINFRA_API_KEY! },+});

  3. Update WebSocket connections

    -const wsUrl = process.env.QN_ENDPOINT!.replace("https://", "wss://");+const wsUrl = "wss://ws.sol.openinfra.sh?api-key=" ++  encodeURIComponent(process.env.OPENINFRA_API_KEY!);

    Server-side WebSocket clients may send x-api-key as an upgrade header instead.

  4. Replace provider-specific streams

    Compare Yellowstone gRPC and Datastream/Eventstream against the exact QuickNode feature you used.