LogoLogo
  • 🖖Introduction
  • Products
    • 💫Cross Chain Swaps
      • Core Solutions and Advantages
      • Single Chain Swaps/Meta-aggregation
    • 👾Bridge
      • Direct Staking
      • Partnership Request
    • 🚀Gas Transfer
    • 💰Farm
      • Stablecoin Pools
      • ITP Farms
    • 🎇ITP Token
      • Contract Addresses
  • Learn More
    • 🤝Integrations
      • LayerZero
      • Circle CCTP
      • Chainlink CCIP
    • 🪐Scalability
      • Interchain Optimal Swaps
      • Automated Arbitrage Pool
      • Interchain Order Book
      • API SDK
      • Cross-Chain DEX Aggregator
    • 👽Socials and Community
    • 🔗Supported Chains
  • Rocket Science
    • 🛰️Technical Implementation
      • Diagrams and Charts
      • Swaps
      • Cross-Chain Message
      • Slippage Optimization
      • Destination Chain
      • Stablecoin Liquidity
      • Variable Token and Variable Balance
      • Events
      • Swap on the Same Network
      • Fee Distribution
      • Manager Role
    • 📃Contracts
    • 🛡️Audits
  • Guides
    • Cross-Chain Trading
    • Bridge
    • Gas Transfer
    • Assets Refund
    • Explorer
    • Testnet Bridge
  • TERMS & PRIVACY
    • Terms of Use
    • Privacy Policy
Powered by GitBook
On this page
  1. Rocket Science
  2. Technical Implementation

Cross-Chain Message

As a result of the actions of the ActionExecutor contract on the initiation chain, data generated is sent to the destination chain to complete the transaction.

To transmit a cross-chain message, one of the cross-chain message providers is used, depending on the message fee price and message delivery time based on data of previous transactions. User can specify which cross-chain message protocol to use on Interport UI.

Cross chain message providers:

  • LayerZero - an omnichain interoperability protocol.

The swap data amount for the destination chain is derived from the amount of stablecoins sent to the Vault contract origin chain, which makes it impossible to compromise the output amount on the destination chain. The algorithm also takes into account the possible difference in decimal numbers of tokens on different networks.

A cross-chain call fee is also accounted for in the execution function call on the ActionExecutor contract. To calculate the payment for the call, the frontend calls the messageFeeEstimate function of the ActionExecutor.

The ActionExecutor contract sends the data and payment for the cross-chain call to the Gateway contract. This contract uses external cross-chain messaging mechanisms to deliver data to a similar Gateway contract on the target network.

The Gateway on the second network receives the data and checks the sender of the message, then calls the handleExecutionPayload function on the ActionExecutor contract on the second network.

PreviousSwapsNextSlippage Optimization

Last updated 1 year ago

🛰️