Symbiosis Documentation
Symbiosis NestDeveloper ToolsGo to Bridge & Swap
  • Getting Started with Symbiosis
  • Symbiosis: Frequently Asked Questions
  • Main concepts
    • Glossary
    • Symbiosis SIS Token
    • Symbiosis sTokens
    • Symbiosis: Cross-Chain Swaps
      • Symbiosis: To/From BTC
      • Symbiosis: To/From TON
    • Cross-Chain Zaps
    • Symbiosis as Interchain Communication Protocol
    • Symbiosis & Fees
    • Security Audits
    • Bug Bounty Program
  • Governance
    • 🚩Governing Symbiosis
  • User Guide (WebApp)
    • Symbiosis WebApp
    • Bridge with Symbiosis: sUSDC, sWETH, sWBTC
    • Swap & Bridge with Symbiosis
    • Swap & Bridge To and From Bitcoin
    • Swap & Bridge To and From Tron
    • Stuck Transactions
    • Bridging SIS Token
    • Symbiosis Liquidity Pools
    • Withdrawing from Symbiosis Octopool
    • Cross-Chain Zaps
    • Common Issues and Solutions
    • Where are My Tokens?
    • Symbiosis Explorer
    • More about Slippage Tolerance
  • Reward Programs
    • Symbiosis Reward Programs
    • Farming on Octopools
    • SIS LP Farming
    • veSIS
  • Cross-chain liquidity engine
    • Symbiosis Core Smart Contracts Overview
    • Symbiosis Mint-Burn Process
    • Symbiosis BridgeV2 Contract
    • Symbiosis Routing Contracts
    • Symbiosis & Emergencies
    • Symbiosis Octopools
  • Relayers network
    • Symbiosis Relayers Network
    • Symbiosis PoS Staking & Symbiotic Staking
      • Symbiosis X Symbiotic: SIS Restaking Vault User Guide
    • Relayers Network: Architecture and Operations
    • Symbiosis Relayer Node
    • Symbiosis Relayers Network: Emergencies
  • Developer Tools
    • Symbiosis Developer Tools
    • Symbiosis API
    • Symbiosis JS SDK
      • JS SDK Types
      • JS SDK Configuration
  • Miscellaneous
    • Symbiosis on Testnet
    • Symbiosis Multisig Address on Scroll
    • Symbiosis v1 vs. v2
  • Follow Us
  • Symbiosis | X
  • Symbiosis | Telegram
  • Symbiosis | Blog
  • Symbiosis | Publish0x
  • Symbiosis | Discord
  • Symbiosis | Linkedin
  • Symbiosis | Github
Powered by GitBook
On this page
  • Cross-chain Zaps
  • Cross-chain Liquidity Withdrawal
  • More Information

Was this helpful?

  1. Main concepts

Cross-Chain Zaps

Symbiosis introduces cross-chain liquidity solutions, empowering users with seamless options for liquidity provision and withdrawal: Cross-chain Zaps and Cross-chain liquidity withdrawal.

PreviousSymbiosis: To/From TONNextSymbiosis as Interchain Communication Protocol

Last updated 19 days ago

Was this helpful?

Curious to see how it works? Check it with

Looking for SDKs and API? Check out our documentation for software developers: Developer Tools

Symbiosis owns liquidity pools () to enable cross-chain operations (swaps, birding, zaps, etc.). Symbiosis Octopools are on the Symbiosis host chain. Liquidity providers supply assets to these pools and receive rewards for it.

Cross-chain Zaps

Cross-chain zapping has been implemented to facilitate liquidity supplying to Symbiosis Octopools located on the Symbiosis Host Chain. Having any assets on any (supported) blockchain, liquidity providers can supply the assets to this pool via cross-chain zapping in one click (one transaction).

For instance, a user has UNI tokens on Ethereum and adds liquidity to the Octopool with sStables on the Symbiosis Host Chain (Scheme 1).

So there is a sequence of steps when doing cross-chain zapping:

  1. Exchange the user's assets for stablecoins on the source blockchain,

  2. Mint sTokens on the Symbiosis Host Chain,

  3. Supply the sTokens to the Symbiosis Octopool with sTokens.

Once the sTokens (sUSDCs in our example) get added to the liquidity pool, the user obtains LP tokens on the Symbiosis Host Chain.

sToken is a type of wrapped token used within the Symbiosis protocol. For more information, please refer to Symbiosis sTokens

Cross-chain Liquidity Withdrawal

This functionality is in the QA stage and will soon be available on the Mainnet.

Cross-chain liquidity withdrawal has been implemented to facilitate liquidity withdrawal from Symbiosis Octopools located on the Symbiosis Host Chain. A liquidity provider can send a transaction that initiates liquidity withdrawal to any blockchain supported by Symbiosis. When the cross-chain operation of liquidity withdrawal is accomplished, the liquidity provider will receive their assets on the blockchain from which the assets were initially added.

Let's consider a liquidity provider has supplied USDC tokens from Ethereum to Symbiosis Octopool on the Symbiosis Host Chain (Scheme 1). There are two ways to withdraw the assets:

  1. The standard procedure involves sending LP tokens to the pool and receiving sUSDC tokens on the Symbiosis Host Chain. Then, the sUSDC tokens can be bridged to Ethereum, and the user receives USDC tokens at a 1:1 ratio minus the cross-chain operation fee. While this method may cost less in terms of cross-chain operation fees, it requires users to have gas tokens to pay transaction fees on the Symbiosis Host Chain and understand how to use sTokens.

  2. A cross-chain way is to send a withdrawal request to any blockchain and get USDC tokens on Ethereum (Scheme 2). The only requirement is that the withdrawal request be sent from an address that matches the address owning the LP tokens on the Symbiosis Host Chain.

More Information

  • For a more detailed explanation, please see Symbiosis Routing Contracts.

If you are curious to see how it works, try our web-based application: .

Symbiosis WebApp
Symbiosis WebApp > Cross-chain zaps
Octopools
Scheme 1. Cross-chain Zap routine of adding liquidity to Symbiosis Octopool.
Scheme 2. Cross-chain liquidity withdrawal routine.