Network family

Bitcoin family errors

Bitcoin-family networks (bitcoin, bch, litecoin, doge, zcash) use bitcoind-style JSON-RPC over HTTPS POST. Only registered read/tx methods are accepted. Common node admin RPCs are intentionally not exposed.

-32601-32600-32002

← 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: uptime"
  }
}

Causes

  • Calling unregistered methods (e.g. help, uptime, wallet RPCs).
  • Extra URL path after the UUID — bitcoin family does not accept path routing.
  • GET instead of POST.
  • Verbose getblock / large getrawtransaction batches hitting upstream limits.

How to fix

  • Stick to catalog methods such as getblockcount, getnetworkinfo, getblock, getrawtransaction, sendrawtransaction.
  • POST to https://{slug}-{env}.{domain}/{uuid} with no trailing path.
  • Use docs pages under bitcoin / bch / litecoin / doge / zcash for credits and params.

Notes

  • Docs content catalogs share the bitcoin method descriptions across bch, litecoin, doge, and zcash slugs.

Related