TriportRPC
DashboardDocs

Robinhood sequencer feed

The live sequencer feed is available from Pro tier at wss://triport.io/ws/robinhood-feed with scope robinhood:feed. Product concurrency is 2 streams on Pro and 4 on Business or Enterprise; these are product limits, not upstream-capacity claims.

Delivery boundary and resume

The service keeps a bounded in-memory replay window: at most 8,192 frames, 64 MiB, or five minutes, whichever limit is reached first. It is not a historical API and the buffer is lost on process restart.

After a disconnect, reconnect with the last fully processed sequence number:

wss://triport.io/ws/robinhood-feed?from_sequence=56798024

The first response is a resume control frame. If resume.bufferComplete is true, the retained buffer covers the requested boundary; replayed data frames have replay: true and contain only sequence numbers greater than the cursor. If it is false, consume the available tail but reconcile the missing range through RPC or your own durable store.

A new live-only connection can first receive a queue-dependent upstream catch-up tail measured at 2.25-111 seconds across three direct-feed windows in September 2026. Compare early transaction age with an independent current head and mark or discard anomalously old transactions.

Frame shape

Data frames have version: 1 and a non-empty messages array. A message includes:

  • sequenceNumber and blockHash;
  • signatureV2 or the compatible signature field;
  • a nested message with header.kind and one of l2Msg, rawTransaction, or rawTransactions.

For l2Msg, the measured binary envelope is described as [0x03][BE64 L][0x04][tx], where L = 1 + len(tx). The role of 0x04 remains unconfirmed. Observed transaction envelopes were legacy, rare 0x01, and mostly 0x02; 0x03 was not observed. Accept unknown types and preserve their frames.

The feed also carries control frames without messages:

  • confirmedSequenceNumberMessage.sequenceNumber is Robinhood's latest confirmed sequence watermark;
  • resume describes Triport replay coverage after a cursor reconnect.

Triport adds a reconciliation object with the latest confirmed watermark, the frame's last sequence, confirmation lag, and the cumulative count of source gaps observed by this process. Treat status: confirmed as confirmation according to the upstream feed watermark, not as a stronger independent finality claim.

Consumer metrics

Track at least connection and reconnect count, frame and message count, last and confirmed sequence numbers, observed gaps, confirmation lag, catch-up-tail duration, decode failures, and time since the last frame. Persist your processed sequence cursor before acknowledging downstream work.

The normative schema is the Robinhood feed AsyncAPI contract.