> For the complete documentation index, see [llms.txt](https://docs.snowsight.chainsight.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snowsight.chainsight.dev/snowsight/services/mempool-stream.md).

# Mempool Stream

Mempool data on Avalanche C-Chain is only shared amongst validator nodes.  When any node receives a pending transaction, it is randomly gossiped to ten other validator nodes in its peer list regardless of stake.\
\
The Mempool Stream solves three core problems for users:

1. Technical: Running a validator is technically difficult and time consuming
2. Capital: Each validator node requires 2000 AVAX to be staked
3. Infrastructure: A single validator node does not provide an accurate view of the mempool

The Mempool Stream solves these problems by aggregating all pending transactions from Snowsight's validator node network and streamlines them into one source for users. &#x20;

Upon connecting to Snowsight, users must authenticate the connection by sending their `'signed_key'`  to the server.  After this, Snowsight will authenticate the connection and begin streaming pending transactions.

The user has the option whether to receive a notification when pending transactions are finalized into a real block by passing a true or false flag in the `'include_finalized'` field when authenticating the connection .  This allows the user to measure the amount of time a transaction was in the mempool before being finalized into a block.&#x20;


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.snowsight.chainsight.dev/snowsight/services/mempool-stream.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
