> For the complete documentation index, see [llms.txt](https://docs.cyclenetwork.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cyclenetwork.io/cycle-network-docs/technical-introduction/technical-background/sequencer.md).
# Sequencer
A sequencer is a specialized entity or component responsible for ordering and managing the sequence of transactions within a blockchain network. The primary role of a sequencer is to ensure that transactions are processed in a specific and consistent order, which is crucial to maintain the integrity and reliability of the underlying blockchain.
Sequencers are particularly important in Layer 2 scaling solutions. In a Layer 2 network, the sequencer collects transactions, orders them, and then submits the ordered block to Layer 1 for the final settlement. This process helps alleviate the congestion on the main blockchain and allows for faster and cheaper transactions.
The sequencer can be operated by a single entity or a decentralized group of participants, depending on the design of the blockchain protocol. In some implementations, the role of the sequencer may rotate among different nodes to enhance security and decentralization.
By ensuring a consistent transaction order, sequencers play a critical role in preventing double-spending attacks and other forms of transaction manipulation. They also contribute to the overall efficiency and scalability of the blockchain network by enabling higher transaction throughput and reducing latency.
---
# 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.cyclenetwork.io/cycle-network-docs/technical-introduction/technical-background/sequencer.md?ask=&goal=
```
`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.