Glacis
  • Overview
  • Glacis Core
    • Why Glacis?
    • Getting Started
    • Concepts
      • Architecture
      • Components
      • Features
        • Abstraction
        • Access Control
        • Redundancy
        • Retry Management
        • Routing
        • xERC20s
      • Governance Model
      • Upgrade Model
      • Security Model
    • Messaging Fees
      • Protocol Fees
      • Gas Overhead
    • Troubleshooting
      • Integration Checklist
      • Error Messages
      • FAQ
    • References
      • Smart Contracts
        • GlacisRouter
        • GlacisClient
        • SimpleTokenMediator
      • Supported Chains
      • Supported GMPS
  • Airlift
    • Why Airlift?
  • Architecture Overview
    • On-Chain Interface
    • Off-Chain Interface
  • Operation Overview
  • Send & Execute
Powered by GitBook
On this page
  1. Architecture Overview

On-Chain Interface

PreviousArchitecture OverviewNextOff-Chain Interface

Last updated 22 days ago

Airlift is available through on the following mainnet chains.

  • Ethereum

  • Optimism

  • Binance Smart Chain

  • Polygon PoS

  • Base

  • Mode

  • Arbitrum

  • Avalanche

  • Linea

  • Scroll

Airlift is exclusively used by LiFi on all chains that LiFi is enabled on. If you would like to use Airlift on a chain that was not listed above, please contact us.

There is a single point of entry for Airlift's smart contracts: the send function.

function send(
    address token, 
    uint256 amount, 
    bytes32 receiver, 
    uint256 destinationChainId, 
    address refundAddress
) payable returns (bytes memory)

This send function allows you to send any token registered to Airlift across chains. The parameters are as follows:

  • token - The address of the token that you wish to send across chains.

  • amount - The amount of the token that you wish to send across chains.

  • receiver - The address of the receiver in bytes32 format. If an ethereum based wallet, encode the address as packed.

  • destinationChainId - The EVM Chain ID of the destination chain. If the destination chain is not an EVM, special IDs will be allocated.

  • refundAddress - The EVM address that the GMP addresses should refund unused cross-chain gas to in case too much was provided.

Note that the send function is payable. Native gas currency must be included to pay for the cross-chain transfer, since the destination chain transfer must be incentivized. The amount required can be estimated via our API's quote endpoint.

LiFi's API