Docs
PricingDashboard

Network family

Other network families

Besides EVM, Solana, Bitcoin, and TRON, RpcNode docs catalogs cover additional protocol families. They share the same platform gateway errors (RPS, IP allowlist, upstream, parse). Method allowlists and HTTP shapes differ per family — always use the methods listed for that network slug.

-32601-32600-32002-32000

← All errors

Example response

Example

HTTP/1.1 404 Not Found
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": null,
  "error": {
    "code": -32601,
    "message": "method not found: unknown_method"
  }
}

Causes

  • Calling a method from another ecosystem (e.g. eth_call on Near).
  • Wrong path vs JSON-RPC mode for families that use REST-like routes.
  • Network slug active in docs content but endpoint environment not ready → upstream -32002 / not configured.

How to fix

  • Open /{slug} for the network and use only listed methods.
  • Apply the same platform troubleshooting for 429 / 403 / -32002 as on EVM.
  • Confirm the endpoint’s network slug matches the docs page you are following.

Families & example slugs in docs catalogs

near → near

aptos → apt

sui → sui

cosmos → cosmos, osmosis, inj, celestia

substrate → dot

starknet → strk

xrpl → xrpl

stacks → stx

stellar → stellar

ton → ton

flow → flow

fuel → fuel

aleo → aleo

Platform codes and messages are identical; only Parse/Forward rules and method registries change per family.

Related