> For the complete documentation index, see [llms.txt](https://docs.bloxroute.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloxroute.com/robinhood/sequencer-feed.md).

# Sequencer Feed

The bloXroute Sequencer Feed provides low-latency access to Robinhood Chain blocks as the sequencer produces them, delivered from bloXroute infrastructure placed close to the sequencer for the lowest latency and variance.

Robinhood Chain has no public mempool, so the sequencer feed is the earliest view of transactions available - streamed before blocks are finalized on-chain.

Available on the Enterprise plan and above. For more details and to get your access token, [contact the bloXroute team](https://docs.bloxroute.com/introduction/contact-us).

**Stream Endpoint**

* Endpoint: `wss://feed.mainnet.chain.robinhood.blxrbdn.com/ws/<account_token>`

Your account token is your credential and goes in the URL path. The token is checked at the WebSocket handshake and the connection is refused if it's wrong. Treat it like a password.

**Examples**

```bash
wscat -c "wss://feed.mainnet.chain.robinhood.blxrbdn.com/ws/<account_token>"
```

Nitro node:

```bash
--chain.id=4663 \
--node.feed.input.url="wss://feed.mainnet.chain.robinhood.blxrbdn.com/ws/<account_token>"
```

**Response**&#x20;

```json
{
  "version": 1,
  "messages": [
    {
      "sequenceNumber": 60163493,
      "message": {
        "message": {
          "header": {
            "kind": 3,
            "blockNumber": 25953369,
            "timestamp": 1789120178
          },
          "l2Msg": "..."
        },
        "delayedMessagesRead": 302149
      },
      "blockHash": "0xc254c996290ae24734283fd46a8db50b40ffcc3327fcabf4f9c61f37483246d7",
      "signatureV2": "PUDdzzMWgNlc...",
      "blockMetadata": null
    }
  ]
}
```

| Field                | Meaning                                                           |
| -------------------- | ----------------------------------------------------------------- |
| `sequenceNumber`     | Position in the feed. Increases by one per frame.                 |
| `header.blockNumber` | The L2 block this message produces.                               |
| `header.timestamp`   | Sequencer time, Unix seconds.                                     |
| `l2Msg`              | The block's transactions, base64, in Nitro's L2 message encoding. |
| `blockHash`          | Hash of the resulting block.                                      |
| `signatureV2`        | The sequencer's signature over the message.                       |

**Optional headers**

* `Arbitrum-Requested-Sequence-Number: <n>` — replay from sequence number n, then continue live.
* `Arbitrum-Feed-Client-Version: 2` — sent by Nitro nodes; optional here.

**Limits:** 5 connections per access token by default.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bloxroute.com/robinhood/sequencer-feed.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.