> For the complete documentation index, see [llms.txt](https://docs.ryoshiresearch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ryoshiresearch.com/welcome/transactions-and-data-flow.md).

# Transactions and Data Flow

The process of validating a specific transaction within the batch typically involves three steps:

1. **Trusted state**

   This state is given by the trusted sequencer almost instantaneously. The state is updated on L2, but has not yet reached L1.
2. **Virtual state**

   Batches have been sequenced and data is on L1. At this point, transactions and data can not be modified as the state is final, yet they are not yet proven and are available on L1 for anyone to prove.
3. **Verified state**

   Zk-proof has been posted on L1, and the smart contract verifies the virtual state, allowing for the withdrawal of funds.


---

# 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.ryoshiresearch.com/welcome/transactions-and-data-flow.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.