[ SUPANODE ]by hightower
▾ Documentation

RPC restrictions

No RPC methods are blocked on Supanode. Heavy methods like getProgramAccounts cost more RPS units; archival mode and multi-region are not available in v1.

// updated 2026-06-04

NOTE
RPC restrictions are validated by Supanode engineering for v1, pending final sign-off before public launch.

What you should know about edge cases on Supanode RPC.

No methods are explicitly disabled

Supanode supports every method in the official Solana RPC spec. RPC traffic is governed by the method weight system rather than a blocklist, so heavy calls stay available but cost more. (For comparison, gRPC and WebSocket do block specific high-traffic subscriptions.)

Methods that touch many accounts or scan large indexes cost more RPS units per call:

  • getProgramAccounts costs 30 RPS units per call.
  • getTransaction costs 10.
  • See Limits for the full table.

This means a 100 RPS plan handles ~100 simple getAccountInfo calls per second, but only ~3 getProgramAccounts calls per second. The plan's price reflects this implicit budget.

Known constraints

  • No archival mode toggle. All Supanode nodes are configured the same way. There's no separate "archival" tier - history depth is what the network provides.
  • Single region in v1. All nodes serve from Frankfurt. Multi-region is on the roadmap.

What you can do instead

  • For heavy-program scans - use gRPC accounts subscription with filters instead of polling getProgramAccounts.
  • For historical replay - getSignaturesForAddress plus per-signature getTransaction works for historical transaction lookups.
  • For TLS-encrypted gRPC streams - Dedicated Node.

See also