AIE Chain
  • AIE Chain SoK
    • Introduction
    • Challenges
      • Blockchain Scalability
      • Gas Issues
      • Unfriendly UX
    • AIE Unique Propositions
    • AIE Chain
      • Building Blocks
      • AIE Chain Architecture
      • AIE Chain Specifications
        • Contracts
        • Contract addresses & RPCs
      • AIE Name Service
      • Bridges
      • AIE Block Explorer
    • AIE Embedded Wallet
      • Account Abstraction
      • Smart Wallet Creation
      • Privacy and Security
      • Gasless Transaction
      • ANS Compatible
      • Export & Import
      • Backup & Recovery
    • AIE Token
    • Onboarding the next billion Web3-users
      • Genesis Marketplace
        • Bring your imagination to life
        • Sign your creative works
        • Mint your creative works into NFT
        • NFTs Marketplace
      • RizzAI: Web3 AI-powered virtual companions
        • Register
        • Log-in
        • Create AI Character
        • View your AI characters
        • Edit your AI character
        • Chat with AI companions
        • Premium Subscription
        • Gallery
      • Rakis: Decentralized Verifiable Inference Network
        • Overview
        • Architecture
        • Data Flow
        • Consensus
      • Interactive AI LiveStreaming
      • Collaborative Content Creations
      • Decentralized Licensing
    • FAQs
Powered by GitBook
On this page
  1. AIE Chain SoK
  2. AIE Chain

AIE Chain Architecture

PreviousBuilding BlocksNextAIE Chain Specifications

Last updated 1 year ago

AIE Chain is an L2 chain that is built based on Arbitrum AnyTrust protocol.

There is a specially designated node, called AIE-Sequencer, responsible for processing transactions and handling smart contracts’ computation on AIE It is critical that the AIE-Sequencer behaves honestly, and that there exists a mechanism for any other node can independently verify this assumption.

The AIE-Sequencer carries out several crucial operations:

  1. Aggregate transactions: Sequencer receives transactions from end users via a mempool.

  2. Order transactions: Sequencer selects transactions from the mempool and arrange them based on a specified policy.

  3. Execute transactions: In many rollups, sequencers are responsible for executing transactions in accordance with the underlying Virtual Machine (VM).

  4. Generate pre-confirmation: Since finality for rollup transactions is ultimately derived from the underlying Layer 1, sequencers often generate pre-confirmation for user transactions. This enables clients and applications to proceed while awaiting finality from Layer 1.

  5. Transmit ordered transaction data to the Data Availability (DA) Layer: As the final step, sequencers commit the ordered transaction data to a DA layer, such as the underlying Layer 1. Once posted on Layer 1, transactions attain Layer 1-level finality.

To ensure the AIE-Sequencer would behave honestly, we leverage ’s restaked primitive that is built atop . The sequencer is required to provide a certain amount of economic collateral, which is slashed if in the presence of any misbehavior.

Besides honest execution, the sequencer also needs to post raw transaction data to a data availability layer, so that it can be accessible by other nodes who wish to verify the smart contract computation outputs and AIE-Chain states. AIE chain relies on for data availability.

Chain.
AltLayer
EigenLayer
EigenDA