DZap Documentation
  • 🌐Overview
  • Features
    • Aggregation
      • Usecases
      • Fee Structure
      • Chains, Bridge and Liquidity
      • Different Transaction Status
      • Price Imapct Handling
      • Technical Details
    • DCA
      • Creating Positions
      • Additional Actions
      • Swap properties
      • Fees
      • Supported Tokens
    • Zapping (Coming soon)
      • Use Cases
      • Liquidity Migration
      • Supported Routes
  • Protocol
    • Contract address
    • Dzap Aggregation API
    • Uniswap Permit V2
    • Backend API
  • Terms & Security
    • Troubleshooting & Self Serve Guide
    • Terms
    • Audit Reports
    • Privacy
    • Security
  • Tutorial
    • Batch Swap via DEX Aggregator
    • Batch swap via Bridge Aggregator
    • Minting LST from Any Chain
  • Socials
    • 🌐Website
    • 🐦Twitter
    • 👾Discord
    • Ⓜ️Medium
  • DZap SDK
    • Dollar Cost Averaging (DCA)
      • Overview
      • Installation
      • Quick Start
      • Usage Guide
      • Methods
      • Data Types
Powered by GitBook
On this page
  • Same-chain Liquidity Migration:
  • Cross-chain Liquidity Migration:
  1. Features
  2. Zapping (Coming soon)

Liquidity Migration

Liquidity providers often need to migrate liquidity between pools or protocols to optimize returns. DZap’s zapping infrastructure simplifies this process significantly:

Same-chain Liquidity Migration:

  • Example: A user wants to migrate liquidity from one Uniswap pool to another. DZap withdraws liquidity from the current pool, swaps the tokens if necessary, and adds liquidity to the new pool in a single transaction.

Cross-chain Liquidity Migration:

  • Example: A user wants to migrate liquidity from an Ethereum pool to a Binance Smart Chain (BSC) pool. DZap handles the withdrawal, bridging, and liquidity provision on BSC in one seamless transaction.

PreviousUse CasesNextSupported Routes

Last updated 5 months ago