> 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/where-is-nova-available/how-it-works-on-l2/nova-on-arbitrum.md).

# Nova on Arbitrum

Nova will route transactions through the Timeboost lane when Kairos is the Timeboost leader

* **Timeboost:** The first wave of centralized sequencers, such as those operated within Base and Arbitrum ecosystems, ordered transactions based on a first come first served (FCFS), and via optional priority fees.\
  \
  However, downsides to FCFS emerged in the form of increased network congestion from searchers spamming the network to take advantage of MEV opportunities. In response, Offchain Labs developed Timeboost – a transaction ordering policy which combines an express lane and an offchain auction to protect users from MEV and reduce network spam, whilst preserving fast block times.&#x20;

* **Kairos:** Built by the same team behind Nova, Kairos is a native integration with Arbitrum Timeboost that offers a streamlined path for searchers and other participants to access express-lane blockspace—without directly engaging in each round-level Timeboost auction. <br>


---

# 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/where-is-nova-available/how-it-works-on-l2/nova-on-arbitrum.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.
