# Architecture

<figure><img src="https://2651778593-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrRVb0fldl9XfSO8HHA0I%2Fuploads%2F82AYMR9Vw15IlDiZWS3f%2FScreenshot%202024-08-27%20at%2011.25.28.png?alt=media&#x26;token=84739a68-75b4-4b57-a618-763bf19876f4" alt=""><figcaption><p>Conla's core concepts</p></figcaption></figure>

### **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.
