Method not found

The RPC node does not recognize the method name in your JSON-RPC request.

Common causes

1. Typo in method name. Method names are case-sensitive. getbalance will fail — the correct name is getBalance.
2. Method not supported. Some RPC providers disable certain methods like getBlock with full transaction details, getSlot subscriptions, or deprecated methods.
3. Deprecated method. Older methods like getConfirmedBlock or getConfirmedTransaction were removed in Solana 1.x. Use their replacements: getBlock and getTransaction.
4. Wrong endpoint. You are sending an HTTP request to a WebSocket-only method (like accountSubscribe), or vice versa.

How to fix

1. Check the method name. Verify spelling and casing against the RPC Methods reference.
2. Use the correct protocol. Subscription methods (*Subscribe / *Unsubscribe) require WebSocket, not HTTP.
3. Check provider documentation. Some providers restrict certain methods on free tiers or require specific plan access.
4. Update deprecated methods:

FAQ

What is -32601? It is a standard JSON-RPC 2.0 error code meaning “Method not found”. It is not Solana-specific.

Why does my method work on one provider but not another? RPC providers can choose which methods to support. Archive methods like getBlock for old slots may only be available on archive-tier plans.

Updated: 2026-10-21