Conla Docs
  • Greetings to Conla Docs
  • About Conla
    • What is Conla?
    • Consumer chain on TON
    • Technical Features
    • Architecture
  • Users
    • Onboarding
      • Install MetaMask
      • Add to MetaMask
      • Faucet tTON
    • Community
  • Developers
    • Quick start
      • Connect to Conla
      • Faucet tBTC
    • AA wallet & Paymaster
      • SDK integration
      • Conla Wallet
    • dApp
      • Write a contract
      • Deploy with Foundry
      • Deploy with Hardhat
      • Verify a contract
    • Run a Conla Node
    • Conla Verifier
  • Reference
    • Sovereign SDK
    • reth
    • Celestia
    • ERC-4337: Account Abstraction
Powered by GitBook
On this page
  • Transaction Submission
  • Transactions Posted to DA Layer
  • Compute State Transition
  • Proof Generation
  • Proof Submission & Verification
  1. About Conla

Architecture

PreviousTechnical FeaturesNextOnboarding

Last updated 8 months ago

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.

Conla's core concepts