> For the complete documentation index, see [llms.txt](https://docs.altlayer.io/altlayer-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.altlayer.io/altlayer-documentation/restaked-rollups/vital-for-decentralised-verification/tier-1-finality.md).
# Tier-1 Finality
To understand this, consider the lifecycle of a rollup transaction on Arbitrum or Optimism today. As these networks operate with a centralized sequencer, the sequencer takes a user’s transaction, processes it and issues a transaction receipt that acts as proof of soft finality. Note that this transaction could either come directly to the sequencer or could come from the L1 (when it is a withdrawal request from Layer 2 -> Layer 1). However, as the soft finality is issued from a single centralized sequencer, the guarantee offered here is mostly a “trust me” guarantee. Also in scenarios, where the sequencer goes unavailable, this guarantee is impossible to obtain in the first place.
On the other hand, as rollups in AltLayer have decentralized sequencers via SQUAD, and as these sequencers themselves can potentially run a consensus protocol amongst themselves, the soft finality guarantee here is in fact slightly “harder” than the corresponding guarantee at the same level from rollups with centralized sequencers. We refer to this finality as Tier 1 finality.
---
# 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.altlayer.io/altlayer-documentation/restaked-rollups/vital-for-decentralised-verification/tier-1-finality.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.