> For the complete documentation index, see [llms.txt](https://docs.roguechain.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roguechain.io/rogue-protocol/rogue-chain/anytrust-revolutionizing-blockchain-infrastructure/sequencer-committee-interaction.md).

# Sequencer-Committee Interaction

When the Arbitrum sequencer initiates posting a data batch through the Committee, it simultaneously dispatches the data, along with an expiration time, to all Committee members via RPC. Each Committee member receives the data, stores it, signs the (hash, expiration time) pair using its BLS key, and returns the signature along with a success indicator to the sequencer.

Upon collecting sufficient signatures, the Sequencer aggregates them to form a valid DACert for the (hash, expiration time) pair. This DACert is then transmitted to the L1 inbox contract, rendering it accessible to the AnyTrust chain software at L2.

In instances where the Sequencer fails to gather enough signatures within the specified timeframe, it adopts a "fall back to rollup" strategy by directly posting the full data to the L1 chain. The L2 software is proficient in understanding both data posting formats (via DACert or full data) and handles each format accordingly.

In essence, AnyTrust, a pioneering innovation within the Offchain Labs ecosystem, signifies a significant leap forward in addressing challenges related to data availability, security, and cost efficiency in blockchain infrastructure. By employing a prudent trust assumption and introducing a fresh approach to data posting, AnyTrust lays the groundwork for more scalable, accessible, and secure blockchain solutions.


---

# 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.roguechain.io/rogue-protocol/rogue-chain/anytrust-revolutionizing-blockchain-infrastructure/sequencer-committee-interaction.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.