AIE Chain Architecture
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 Chain. 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:
Aggregate transactions: Sequencer receives transactions from end users via a mempool.
Order transactions: Sequencer selects transactions from the mempool and arrange them based on a specified policy.
Execute transactions: In many rollups, sequencers are responsible for executing transactions in accordance with the underlying Virtual Machine (VM).
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.
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 AltLayer’s restaked primitive that is built atop EigenLayer. 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 EigenDA for data availability.
Last updated