> For the complete documentation index, see [llms.txt](https://docs.artemisfinance.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.artemisfinance.io/backgroud/metis/decentralized-sequencer.md).

# Decentralized Sequencer

The evolution of scalability solutions on Ethereum began with State Channels, followed by Sidechains and Plasma. While these solutions addressed scalability, they came with complexities and limitations. Rollups, specifically Optimistic Rollups and zk-Rollups, emerged as promising Ethereum Layer 2 scaling solutions.

A sequencer plays a crucial role in managing and ordering transactions. In a Layer 2 scaling solution, transactions are processed off-chain to improve scalability, but there is a need for a mechanism to keep track of the correct order of these off-chain transactions before they are finalized on the main blockchain.

The sequencer acts as a coordinator or orderer in the Layer 2 network. It is responsible for collecting and organizing transactions from users or participants before submitting them to the main blockchain. This helps ensure that the transactions are executed in the correct sequence, maintaining the integrity and consistency of the overall transaction history.

However, the challenge with a centralized sequencer is that it introduces a potential single point of failure and centralization risk. If the sequencer is compromised or experiences downtime, it can impact the entire Layer 2 network. 

To address these concerns, Metis is poised to become the first Ethereum rollup to decentralize its sequencer, addressing security concerns and promoting community involvement. This shift enables features like seamless sequencer rotation, improved network stability, and revenue sharing through a Proof-of-Stake Sequencer Pool.

<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 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.artemisfinance.io/backgroud/metis/decentralized-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.