Pending data

pending is a snapshot of what the sequencer presents right now. It is not a durable stage, public mempool, or finality signal. A pending block or transaction can disappear, be replaced, or move into another block; its hash may be null and may later change.

Endpoint and plans: Robinhood Chain RPC endpoint.

In the 2026-09-15 M1 snapshots — internal per-PoP diagnostics for US and EU — no operator with a valid pending/latest comparison exposed pending ahead of latest from either PoP. Some responses were stale and some operators could not provide a valid latest marker. For that reason the robinhood_pendingBlock stream remains disabled by default; only an operator can enable it after a fresh measurement.

Robinhood does not expose a contracted txpool_* surface, and newPendingTransactions is not available. The opt-in robinhood_pendingBlock subscription is a Triport snapshot stream when enabled; see WebSocket subscriptions. The sequencer feed carries already assembled L2 blocks and must not be treated as a pending pool.

Reconcile by transaction hash against later canonical blocks and apply your own confirmation policy before treating state as final.