For the complete documentation index, see llms.txt. This page is also available as Markdown.

Provide Liquidity to Symbiosis Octopools

This guide explains how to provide liquidity to Symbiosis Octopools, how address for LP tokens work, and how to withdraw liquidity from pools.

Symbiosis Octopools Overview

Symbiosis uses Octopools for cross-chain operations. Each cross-chain transaction goes through an Octopool located on the Symbiosis chain, also referred to as the Symbiosis Host Chain.

An Octopool is a multi-token pool. There are three main Octopools:

  • With stable coins (USDC, USDT, etc.) bridged from supported chain,

  • With wETH tokens bridged from supported chain,

  • With wBTC bridged from supported chains

The easiest way to view supported tokens and chains is through the Pools section in the Symbiosis WebApp:

  • Token: the token available for liquidity provision.

  • Chain: the chain from which the token can be supplied.

  • Data relaited to the token:

    • Total Locked: total tokens locked in the pool.

    • Pool Balance: current balance ratio for this token in the pool. It affects deposits, withdrawals, and route availability.

    • APR: annual percentage rate for liquidity provision.

How Liquidity Is Added

Symbiosis Octopools are located on the Symbiosis chain. Because of this, when liquidity is supplied from another blockchain, the token first needs to be moved to the Symbiosis chain and then added to the pool.

In the standard WebApp flow, this is done in one deposit operation:

  1. The source token is locked in a dedicated contract on the source network.

  2. The bridged token is minted on the Symbiosis chain.

  3. The token is added to the Octopool.

  4. LP tokens are issued on the Symbiosis chain and sent to the user's address.

Advanced users can also do this manually in two steps: bridge the token to the Symbiosis chain first, then add it to the pool.

Address for LP tokens

When liquidity is added, LP tokens are issued on Symbiosis chain. These tokens are required to withdraw your assets, so make sure they are sent to an address you control.

If you add liquidity from an EVM EOA wallet, LP tokens are sent by default to the same EVM-compatible address on the Symbiosis chain.

If you add liquidity from a non-EVM network, such as Solana or TON, provide an EVM-compatible address on the Symbiosis chain to receive LP tokens.

Using a multisig wallet

If you manage your LP tokens through a multisig wallet, make sure you have a multisig deployed on the Symbiosis chain. A multisig on the source network may not exist at the same address on the Symbiosis chain.

You can create your own Safe wallet on the Symbiosis chain at https://safe.symbiosis.finance/

Important: Make sure your Safe wallet is deployed and you can execute transactions from it before adding liquidity. You will need it to manage your LP tokens and withdraw your assets.

Setting a custom LP token receiver

To send LP tokens to a different address:

  1. Enable Receive LP tokens to another wallet in the WebApp.

  2. Enter the recipient address on the Symbiosis chain.

  3. Confirm that you control the recipient address.

Depositing Liquidity

To deposit liquidity to a Symbiosis Octopool:

  1. Connect your wallet.

  2. Find the token and chain you want to supply liquidity for, then press Manage (for example, WETH on Arbitrum One):

  3. Enter the amount to deposit: Important: If a multisig contract is used to sign transactions, provide a valid address on the Symbiosis chain for receiving LP tokens. Multisig contract addresses often differ between the source blockchain (where liquidity is sent from) and the destination blockchain (the Symbiosis chain). To set a custom LP token address, enable the switch in the WebApp and enter a valid address you control:

  4. If prompted, press Switch network to <Network name> and confirm in your wallet.

  5. If prompted, press Approve <Token name> button and confirm in your wallet.

  6. Review the details, then press Add liquidity and confirm in your wallet.

  7. Wait for confirmation — liquidity is added to the pool.

  8. To check, go to Symbiosis WebApp > the Pools tab > My Liquidity to view your deposits:

Done ∎

Withdrawing Liquidity

Symbiosis Octopools are hosted on the Symbiosis chain. Liquidity can be withdrawn only on this chain.

About gas on the Symbiosis chain:

The network uses SIS as its native gas token (bridged from Ethereum). SIS can be obtained in two ways:

  1. Via the official L2 bridge at https://symbiosis.bridge.caldera.xyz/

Withdrawal Process

Liquidity withdrawal has two steps:

  1. Remove liquidity from the pool.

  2. Bridge sTokens (e.g., sUSDC, sWETH, sWBTC) into the corresponding native assets (USDC, WETH, WBTC, etc.). Do not miss the instructions below: Bridging sUSDC, sWETH, sWBTC, etc.

Preparing your wallet for the Symbiosis chain

LP tokens are issued on the Symbiosis chain. To manage them and withdraw your liquidity, you need access to this network and some SIS tokens to pay transaction fees.

Adding the Symbiosis chain to your wallet

If the Symbiosis chain is not already available in your EVM wallet, you can add it manually using the following settings:

In your wallet, open the network settings, select the option to add a custom network, enter the details above, and save.

Getting SIS for gas fees

SIS is the native gas token of the Symbiosis chain. You need SIS in your wallet on this network to pay transaction fees when managing LP tokens or withdrawing liquidity.

You can obtain SIS on the Symbiosis chain through:

Important: Make sure you have enough SIS on the Symbiosis chain before withdrawing liquidity. If your LP tokens are held in a Safe wallet, the Safe itself needs SIS to execute transactions.

Removing Liquidity

To withdraw liquidity from Symbiosis Octopool:

  1. Press Manage for the asset you want to withdraw.

  2. Press Remove:

  3. Select the amount to withdraw (e.g. 75%):

  4. If prompted, press Switch network to <Network name> and confirm in your wallet.

  5. Press Remove and confirm in your wallet.

  6. Wait for confirmation — liquidity is removed from the pool.

Note: When liquidity is withdrawn, you receive sTokens (e.g., sUSDC, sWETH, sWBTC) on the Symbiosis chain. These can be bridged 1:1 to their native tokens (USDC, WETH, WBTC, etc.). See instructions below for bridging.

Done ∎

Bridging sUSDC, sWETH, sWBTC, etc.

When liquidity is withdrawn from Octopools, you receive sTokens (sUSDC, sWETH, sWBTC, etc.) on the Symbiosis chain. These sTokens can be bridged 1:1 back to their native tokens (USDC, WETH, WBTC, etc.) on your target network.

To bridge sTokens:

  1. Go to the Bridge section in Symbiosis WebApp: https://app.symbiosis.finance/bridge Important: The Bridge section is different from the Swap (Exchange) section https://app.symbiosis.finance/swap

  2. Connect your wallet.

  3. In Transfer From, select the Symbiosis chain and choose the sToken to bridge (e.g., sWETH).

  4. In Transfer To, select the destination token (only one option is available for each sToken type, e.g., sWETH → WETH on Arbitrum One).

  5. Enter the amount to bridge:

  6. Press Burn, then confirm the transaction in your wallet.

  7. Wait for confirmation — the tekens are bridged to the destination network.

You can always check status of your cross-chain operations in Symbiosis Explorer.

Getting Support

1. Security Precautions

Never share your seed phrase, private keys, or wallet recovery information with anyone, including people claiming to represent Symbiosis.

Only contact support through the official channels listed below. Be cautious of unsolicited private messages from people claiming to be support team members.

2. Official Support Channels

If you have a question or need help with a swap, contact the Symbiosis support team through one of the official channels below:

3. What to Include in Your Support Request

To help us investigate and resolve your issue faster, please provide:

  • The transaction hash or a link to the transaction in the relevant block explorer or Symbiosis Explorer.

  • The sender's wallet address.

  • Relevant screenshots showing the issue.

Last updated

Was this helpful?