### **Transaction Submission**
Conla sequencers collect transactions from users and order them into rollup blocks.
### **Transactions Posted to DA Layer**
Conla sequencers continuously publish transactions to the DA layer without waiting for proofs. They receive a portion of gas fees (and MEV) as a reward.
### **Compute State Transition**
Conla full nodes read the DA layer for new transactions and execute the changes to the rollup's state. This provides transaction finality quickly to users.
### **Proof Generation**
Conla verifier monitor the DA layer for transactions. They compete against each other to generate a proof that verifies the rollup's new state and receive a portion of gas fees as a reward.
### **Proof Submission & Verification**
Conla verifier submits a rollup transaction that contains the proof as an argument to TON, which verifies the proof.
---
# Agent Instructions: 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:
```
GET https://docs.conla.com/about-conla/architecture.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.