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
    • 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
    • Gasless Crypto Exchanges
  • Follow Us
  • Symbiosis | X
  • Symbiosis | Telegram
  • Symbiosis | Blog
  • Symbiosis | Publish0x
  • Symbiosis | Discord
  • Symbiosis | Linkedin
  • Symbiosis | Github
Powered by GitBook
On this page
  • What are Cross-Chain Zaps?
  • Adding Liquidity via Cross-Chain Zaps
  • Tracking and Troubleshooting Cross-Chain Zaps
  • Guaranteed USDC / USDT / WETH / WBTC
  • Withdrawing Liquidity
  • Getting Support

Was this helpful?

  1. User Guide (WebApp)

Cross-Chain Zaps

Symbiosis guide: Cross-chain Zaps

PreviousWithdrawing from Symbiosis OctopoolNextCommon Issues and Solutions

Last updated 7 days ago

Was this helpful?

What are Cross-Chain Zaps?

For common questions and solutions, check out our

Cross-chain Zaps let you supply assets to lending, farming, or staking protocols across different blockchains.

Powered by Symbiosis, cross-chain Zaps allow you to use any asset on any blockchain and supply it in just one click (a single transaction) to protocols like lending platforms, or farming pools.

Supported Protocols:

  • Lending protocols: AAVE,

  • Farming protocols: BEEFY,

  • Liquid staking protocol: LIDO

Adding Liquidity via Cross-Chain Zaps

Requirements:

  • Ensure you have enough native assets in your wallet to pay for transaction fees on the source network.

Steps to Add Liquidity to a Protocol via Symbiosis:

  1. Navigate to .

  2. Connect your wallet.

  3. Select the Source Token: In the Transfer from field, choose the token you want to supply, and enter the desired amount. For example:

  4. Select the Destination Protocol: In the Supplying to field, select the type of protocol: Lending protocols, Farm, or Liquid staking. Choose the specific protocol and the token you want to supply. For instance, select Farm > BEEFY on the BNB chain:

  5. Review the cross-chain zap details:

  6. Handle Multisig Contracts (If Applicable) If you use a multisig contract to sign transactions, make sure to provide a valid address that you can access on the destination chain for LP tokens or proof of liquidity addition. Note: Multisig contract addresses may differ between the source blockchain (where liquidity is sent) and the destination blockchain (where liquidity is supplied). To change the address on the destination chain, click the cog icon next to the address: Enter a valid address (the address you have access to) and save the changes.

  7. If you see the Switch network to... button, switch to the network by pressing the button and confirming the action in your connected wallet.

  8. If you see the Approve... button, approve the token use by pressing the button and approve the transaction in your wallet. As soon as the transaction is executed, the Add Liquidity button becomes available.

  9. Press the Add Liquidity button, and confirm the transaction in your wallet.

  10. After a short processing time, you will receive a confirmation that the liquidity has been added.

  11. To check the history of your cross-chain operations, please use .

Done ∎

Tracking and Troubleshooting Cross-Chain Zaps

About Symbiosis Explorer

Symbiosis Explorer collects and analyzes data from cross-chain operations performed via the Symbiosis protocol across all supported networks. It provides a detailed status of each operation, helping you track your transactions.

Stuck: What Does It Mean?

Generally, the "Stuck" status on a cross-chain operation indicates that the operation is taking longer than usual but is still likely to be completed.

Guaranteed USDC / USDT / WETH / WBTC

In rare cases, you may receive stablecoins (USDC, USDT), WETH, or WBTC on destination network instead of the tokens being supplied to the selected protocol.

Why Does This Happen?

Cross-chain operations involve exchanging assets between different blockchains, and these operations are not instantaneous. If the exchange rate on the destination network changes during the processing time and the new conditions no longer meet the stated ones, or if the selected protocol doesn't accept tokens, the Symbiosis protocol will deliver a stablecoin, WETH, or WBTC to the specified address on the destination network.

Why stablecoins, WETH, or WBTC tokens?

Stablecoins, WETH and WBTC tokens have the same face value across different networks, making them ideal transit tokens for routing cross-chain operations within the Symbiosis protocol.

Withdrawing Liquidity

Cross-chain Zaps cannot be used for withdrawing liquidity, as liquidity withdrawal is primarily an on-chain operation.

To withdraw liquidity, use the respective lending or farming protocol directly.

Getting Support

Remember, never share your pass phrases or any other sensitive information with anyone.

Use the to track your cross-chain operation.

If you don't mind waiting a bit longer, we recommend using the to monitor the status of your cross-chain operation. Alternatively, if you prefer to retrieve your tokens as soon as possible, the option to undo the operation will become available 10 minutes after the "Stuck" status is assigned. For detailed instructions on how to revert stuck tokens, refer to Stuck Transactions

If you have any questions or issue, please contact .

For common questions and solutions, check out our

Symbiosis Explorer
Symbiosis Explorer
our support team on Discord
FAQ and Troubleshooting Guide
FAQ and Troubleshooting Guide
Symbiosis WebApp > Zap
Symbiosis Explorer