> For the complete documentation index, see [llms.txt](https://docs.singularityfinance.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.singularityfinance.ai/sfi-l2/l2-architecture/sequencer.md).

# Sequencer

####

The sequencer serves as a critical component of the rollup architecture, batching and ordering transactions before submitting them to the Ethereum mainnet. Singularity Finance’s sequencer design prioritises fairness, decentralisation and performance.

Key **Features**:

1. Transaction Ordering: Prevents front-running and MEV (Miner Extractable Value) by implementing fair ordering algorithms.
2. Low Latency: Reduces the time it takes for transactions to be confirmed by processing them offchain in near real-time.
3. Decentralised Sequencing (Future Upgrade): Initially run by trusted operators, the sequencer role will transition to a decentralised network of participants to enhance security and censorship resistance.

<br>

Operational Flow:

1. User Transactions: Submitted to the L2 through wallets or dApps.
2. Batch Formation: The sequencer aggregates multiple transactions into a batch.
3. State Commitment: Generates cryptographic proofs and submits them to Ethereum.
4. Fraud Challenges: Validators can challenge incorrect proofs, ensuring trustless dispute resolution.


---

# 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.singularityfinance.ai/sfi-l2/l2-architecture/sequencer.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.