Paxeer XDocs
Which Ethereum JSON-RPC methods are unsupported?

Unsupported Ethereum JSON-RPC methods

Five methods are registered on the Paxeer EVM endpoint but return a JSON-RPC error with code -32000 instead of a result. Tooling therefore sees a stable, documented failure and not method not found (-32601).

Explicitly unsupported methods
MethodTypical Error MessageReason
eth_blobBaseFee"blobs not supported on this chain"EIP-4844 blob transactions not supported
eth_newPendingTransactionFilter"eth_newPendingTransactionFilter is not supported on Pax EVM RPC"Only on nodes without a receipt-log feed; sequencer and standby nodes serve it (see below)
debug_getRawBlock"debug_getRawBlock is not supported on Pax EVM RPC"Raw RLP block payloads not served
debug_getRawHeader"debug_getRawHeader is not supported on Pax EVM RPC"Raw RLP header payloads not served
debug_getRawReceipts"debug_getRawReceipts is not supported on Pax EVM RPC"Raw RLP receipt payloads not served
What the error looks likejsonReady
1{2  "jsonrpc": "2.0",3  "id": 1,4  "error": {5    "code": -32000,6    "message": "blobs not supported on this chain"7  }8}
From Unsupported JSON-RPC Methods › Error Response Format
Two methods that do work

eth_syncing returns false when consensus reports the node caught up, and otherwise a progress object. debug_getRawTransaction returns raw transaction bytes by hash. See Synchronization and raw transactions.

Ask next

2 blocks are shown verbatim from the documentation, and every identifier in the text was found there.

Reviewed answer
Unsupported Ethereum JSON-RPC methods · Paxeer X Docs