Contracts

This section gives a brief overview of the key smart contracts AIE Chain uses to interface with the Ethereum network (i.e., the L1)

• Cross Chain Messaging Contracts: The pair of contracts are deployed on the L1 and L2, respectively. They function as an interface for handling cross-layer communication between L1 and L2. They offer capabilities to send and receive messages, potentially enabling interactions such as token transfers or contract calls between different network layers.

  • Ethereum-to-Arbitrum messaging: For arbitrary L1 to L2 contract calls, it is often the case that upon publishing the L1 transaction, the L2 side will typically get included within minutes. In common cases, the L2 execution will automatically succeed. For uncommon cases, we refer readers to Arbitrum's docs for detailed discussion.

  • Arbitrum-to-Ethereum messaging: L2 contracts can send arbitrary messages for execution on L1. These are initiated via calls to the ArbSys precompile contract's sendTxToL1 method. As we make a trust assumption on the Sequencer, a L2 transaction can be deemed succeeded as soon as the Sequencer confirms that transaction.

• ERC721 Bridge: The contract enables ERC721 token transfers between L1 and L2 by escrowing tokens on L1, coordinating with the L2 bridge, and ensuring secure and transparent transfers. This contract is crucial for scaling NFTs and ERC721 assets across different blockchain layers.

• ERC Gateway contracts: There is an L1 ERC Gateway contract deployed on the L1 network, and a corresponding L2 ERC Gateway contract deployed on AIE Chain. The pair manage ETH and ERC20 transfers between L1 and L2.