RPC error -32601: robinhood_pendingBlock is not enabled
Last updated:
At a glance
| Property | Value |
|---|---|
| Applies to | Robinhood Chain (chain ID 4663) |
| JSON-RPC code | -32601 |
| Default state | Disabled |
| Alternatives | newHeads (Basic+), sequencer feed (Pro+) |
Cause
robinhood_pendingBlock is an operator-controlled extension, not a standard subscription. When it is disabled, eth_subscribe returns this JSON-RPC error. It is a changing snapshot of the block being assembled, and it is never a mempool or a finality signal.
Solution
- Subscribe to newHeads for confirmed block headers, which is available from Basic tier.
- Use the sequencer feed (Pro and above) when you need assembled L2 blocks with a resumable cursor.
- If your use case genuinely needs pending-block snapshots, raise it with the operator — enabling it shares the newHeads budget.
Example
{
"jsonrpc": "2.0",
"id": 1,
"error": {
"code": -32601,
"message": "robinhood_pendingBlock is not enabled"
}
}FAQ
- Is this a mempool?
- No. newPendingTransactions and txpool_* are not part of the Robinhood contract, and the pending block is a changing snapshot, not a transaction pool.
- Can I enable it myself?
- No. It is operator-controlled, and when enabled it shares the newHeads delivery budget.