Torch Finance Docs
  • Overview
  • Terms of Use
  • Getting Started
    • Introduction
    • Challenges on TON
    • Solution for TON
    • Architecture
      • Concept
      • Core Components
        • Factory
        • Vault
        • Pool
        • LP Account
        • Oracle
      • Comparison
      • Interoperability
      • Meesage Flows
        • Deposit
        • Swap
        • Withdraw
        • Cross-Pool Operations
  • Developer Guide
    • DEX SDK Guide
      • Setup
      • Perform Swap
      • Deposit Liquidity
      • Withdraw Liquidity
      • How to send transaction
        • Mnemonic (Node JS)
        • TonConnect (React)
      • Deployments
  • USER Guide
    • Getting Started
  • Protocol
    • Audits
    • Tokenomics
  • Other
    • Brand Kit
    • Contacts
    • Achievements
  • FAQ
    • How to get Transaction hash by Message hash
    • React (Vite) - Buffer Issues
Powered by GitBook
On this page
  • Efficient Interactions Between Internal Pools
  • Flexible Integration with External DeFi Protocols
  1. Getting Started
  2. Architecture

Interoperability

Seamless Interoperability Across DeFi Protocols

PreviousComparisonNextMeesage Flows

Last updated 3 months ago

Torch Finance is designed with interoperability in mind, facilitating efficient interactions not only between internal pools but also enabling seamless integration with external DeFi protocols.

Efficient Interactions Between Internal Pools

Torch Finance pools are capable of direct communication and collaboration, minimizing the need for repeated asset transfers between contracts, which reduces additional costs and delays.

  • Asset transfers occur only after all cross-pool calculations are complete, significantly saving on gas fees for users.

  • Current cross-pool operations include interactions between Base Pools and Meta Pools, allowing liquidity to flow smoothly between pools and improving capital efficiency.

  • More details: Refer to the for a detailed explanation of the processes

Flexible Integration with External DeFi Protocols

Torch Finance supports interaction with external DeFi protocols through a payload mechanism designed for deposit and swap operations.

  • Fulfill Payload: Upon successful transactions, Torch Finance packages user-defined parameters or data into a fulfill payload and sends it to the user’s specified contract or address. The receiving contract can execute follow-up actions, such as depositing assets into another protocol or executing custom logic.

  • Reject Payload: In case of failed or incomplete transactions, Torch Finance sends a reject payload containing custom rollback parameters or recovery data. The receiving party can use this information to manage assets or trigger rollback procedures.

This design allows users to customize payload parameters during asset swaps or deposits, enabling Torch Finance to interact flexibly with other DeFi protocols. This not only enhances transaction versatility but also positions Torch Finance as a more scalable liquidity solution.

Cross-Pool section