> 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/~/changes/wXds4MSVojVC094qYPIR/beacon-layer/overview.md).

# Overview

<figure><img src="/files/nBns2OlLjBTtF9cVpwFl" alt=""><figcaption></figcaption></figure>

Beacon Layer is an *interlayer* between the execution layer and the data availability layer and all the rollups instantiated via AltLayer are enshrined to the Beacon Layer. The term “enshrined” here refers to the fact that the state of any rollup launched via AltLayer can be verified directly by the Beacon Layer. Additionally, there is an enshrined bridge on the Beacon Layer per rollup.&#x20;

<figure><img src="/files/eEunHehETP4zsnOnTL51" alt=""><figcaption></figcaption></figure>

Moreover, as an interlayer between the execution and the data availability stack, the Beacon Layer provides the following main services:

1. Shared Sequencing Layer
2. Verification Layer
3. Staking/Slashing Layer
4. Interoperability Layer
5. Upgradeability Layer
6. Social Consensus Layer


---

# 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/~/changes/wXds4MSVojVC094qYPIR/beacon-layer/overview.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.