Cross-chain Zaps | Symbiosis
Cross-chain Zaps automate liquidity supplying to the liquidity pools owned by Symbiosis.


Zaps are used to add liquidity to liquidity pools or DeFi protocols. A Zap can contain a few on-chain operations packed in one transaction. Zaps are processed by smart contracts that implement Zap protocol functionality.
Without Zaps: While adding tokens to a liquidity pool, users can only add tokens of the type contained in the pool (Scheme 1).
Scheme 1. Adding liquidity to a liquidity pool without Zaps
If the user has another tokens (e.g. BNB), the user should swap BNB for DOGEs and/or CAKEs first on DEXes of the user’s choice and only then add tokens to the liquidity pool.
With Zaps: While adding tokens to a liquidity pool, users can send any token. The origin token will be swapped to a needed one and added to a liquidity pool on behalf of the user (Scheme 2).
Scheme 2. Adding liquidity to a liquidity pool with Zaps.
Common Zaps are on-chain operations. If you would like to add liquidity located on one blockchain to a liquidity pool located on another blockchain in one transaction, you need cross-chain Zaps.

Cross-chain Zaps

Symbiosis owns liquidity pools with {stablecoin <> sToken} pairs to perform cross-chain swaps. Symbiosis implemented cross-chain Zaps to add liquidity to these liquidity pools from blockchains supported by Symbiosis. Scheme 3 illustrates an example of the cross-chain Zap routine. The user can send any token.
Scheme 3. Cross-chain Zap routine of adding liquidity with Symbiosis protocol.
Once tokens get added to the liquidity pool, the user obtains LP tokens on Binance.
For more detailed explanation how cross-chain Zaps work, please refer to Metarouter V3 | Symbiosis > section Cross-chain Zaps.
There is a user guide on how to add liquidity using cross-chain Zaps: Cross-chain Zaps

Liquidity withdrawing

Zaps are not participating in liquidity withdrawing. While withdrawing liquidity, a user gets liquidity in the token types contained in the liquidity pool. Liquidity withdrawing is always an on-chain operation (Scheme 4).
Scheme 4. Liquidity withdrawing.
Once the transaction gets executed the user receives DOGEs and / or CAKEs (depending on the user's request and LP settings).