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

# Eliminating Mempools

A key feature of Keeta Network is the elimination of memory pools, or "mempools." In traditional blockchain networks, mempools serve as waiting areas for transactions before they're added to a block. This can lead to delays and increased transaction fees during periods of high network activity. Keeta's architecture bypasses this issue entirely. By leveraging the [DAG structure](https://docs.keeta.com/architecture/data-structure.md) and advanced [consensus mechanism](https://docs.keeta.com/architecture/consensus.md), transactions can be quickly validated and incorporated into the network without the need for a mempool intermediary. The result is fast transaction processing and significantly reduced fees.

<figure><img src="https://content.gitbook.com/content/pitcpcamWc0BKEe28I1D/blobs/Pi7P8P1KKkdfAvAzXJg9/image.png" alt=""><figcaption><p>Traditional blockchains utilize mempools as waiting areas for transactions.</p></figcaption></figure>


---

# 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.keeta.com/scalability/eliminating-mempools.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.
