> 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.md).

# How it Works on L2

The majority of L2 rollups rely on centralized, single party sequencers to order and execute transactions, thus eliminating the need for builders and a public mempool.

Without visibility into pending transactions, MEV participants cannot effectively identify or execute front-running/sandwiching opportunities. However, back-running, which does not require seeing a transaction before it is executed remains, and may even be more likely to occur on L2  due to the cheaper gas which makes the point at which opportunities become profitable for searchers lower.

**For this reason, Nova's searcher auction and back-running rebates run on L2.**\
\
To get started, simply switch out the existing sequencer endpoint to the Nova endpoint. Please contact us at **<onboard@novaflow.xyz>** to start benefiting from MEV protection and capture on L2 today.


---

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