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?
    • Supported Chains & Tokens
  • Architecture Overview
    • On-Chain Interface
    • Off-Chain Interface
  • Operation Overview
  • Send & Execute
Powered by GitBook
On this page

Send & Execute

The natural progression of Airlift's token send function includes execution with that token on the destination chain: regardless of whether the user intends to swap, stake, vault, or farm their tokens.

Airlift's send & execute functionality is still in development. Please reach out to us directly!

Some token standards already have a send + execute functionality built in. When sending & executing with these standards, Airlift will default to using the built-in rails.

The token standards that do not implement this sort of functionality must be temporarily escrowed before a secondary cross-chain instruction arrives via Glacis core or an alternative protocol. To escrow properly, all transactions will be done through a smart wallet designated to the original user.

PreviousOperation Overview

Last updated 2 months ago