> For the complete documentation index, see [llms.txt](https://docs.novarpc.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novarpc.xyz/nova-rpc/how-it-works.md).

# How it Works

* **Auction:** Nova routes transactions into a private bidding process where vetted searchers analyse the transaction and market for potential back-running opportunities. Searchers submit bids representing the value they are willing to return, and the highest bidder provides the optimal backrun.\
  \
  Nova bundles the user’s transaction with the winning backrun and submits the package to a trusted builder network, ensuring the user transaction, backrun, and associated refund are included atomically in the same block.\
  \
  This structure prevents harmful forms of MEV such as front-running and sandwich attacks, while allowing transaction originators to capture value generated by the signal their own transaction creates.\ <br>
* **Gas Recoveries:** OFA platforms must request gas recoveries from block builders. Without accurate insight into current block construction dynamics requests are simply estimates based on historical data. \
  \
  Nova minimizes execution uncertainty by dynamically optimising priority fees using real-time intelligence.&#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 by asking a question.

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

```
GET https://docs.novarpc.xyz/nova-rpc/how-it-works.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.