Fast submission
Robinhood sequencing is first-come, first-served (FCFS). A larger priority fee does not move a transaction forward in the sequencer queue. Keep submission connections warm and prepare/sign before the critical path.
Endpoint and plans: Robinhood Chain RPC endpoint.
Triport keeps active HTTP targets warm with probes and maintains a dedicated warm WebSocket submission target. Ordinary raw submission is an earliest-success fan across eligible paths. Conditional requests use only conditional-capable paths and are always dispatched per item; clients use POST /rpc/robinhood and do not configure upstream hosts.
M1 submission timing
These are response times for the deliberately invalid 0x00 probe, not valid-transaction acceptance or inclusion latency. The measurement was taken 2026-09-15 from the named PoP.
| PoP / target class | Warm median | Cold median | Source |
|---|---|---|---|
| US / sequencer intake | 14.6 ms | 42.3 ms | US M1 submit diagnostics (internal) |
| US / public-node WebSocket | 29.3 ms | 56.6 ms | US M1 submit diagnostics (internal) |
| EU / sequencer intake | 101.7 ms | 304.1 ms | EU M1 submit diagnostics (internal) |
| EU / public-node WebSocket | 109.6 ms | 141.4 ms | EU M1 submit diagnostics (internal) |
The route winner depends on PoP and current path conditions; the table is a dated observation, not an SLA. For latency-sensitive FCFS races, use the US entry point because the sequencer is in us-east-2 (internal integration note 07, §5).
For batches, every conditional-containing target batch is split into independent single-item transport requests. An invalid conditional element receives its own response and does not suppress unrelated elements.
Use the generated eth_sendRawTransaction reference for ordinary submission and eth_sendRawTransactionConditional for conditional submission. Submit once and reconcile by transaction hash; retry transport failures explicitly, but do not retry deterministic validation or transaction rejections.