Cross-Chain Liquidity Migration Tool
Free to download on every platform. Comes pre-installed on BotFone, BotPad and BotFlip — with extra free apps included.
About this app
WHAT IT DOES
Cross-Chain Liquidity Migration Tool is a DeFi utility that moves liquidity positions from one EVM chain to another. It reads your wallet address, source token balances, and existing pool positions (supporting Uniswap V2/V3, Curve, and Balancer). The tool then reads destination chain token addresses, pool addresses, and bridge contract status. It estimates gas for all migration steps and checks your existing migration records. The tool guides you through a six-step process: approve token spend on the source chain, transfer tokens to the bridge contract, initiate the bridge transfer, receive wrapped tokens on the destination chain, add liquidity to the destination pool, mint LP tokens, and transfer any remaining dust back to your wallet. All steps are presented in a single review screen before you sign any transaction.
HOW TO USE
Connect your wallet via the built-in connector. Select the source network from the dropdown. Enter the source token address and the source liquidity pool address. Choose the destination chain from the dropdown, then enter the destination token address, destination pool address, and the bridge contract address. The tool will read your balances and pool positions, then display a comprehensive preview including source token, source pool, your balance, destination chain, destination token, destination pool, bridge contract, and estimated total gas. Review the migration steps: approve, bridge, receive, add liquidity, mint LP, and dust transfer. Click "migrate liquidity" to execute the entire workflow. The tool will prompt you to sign each transaction sequentially, with progress updates shown for every step.
TECHNICAL MECHANISM
The tool uses ethers.js v5.7.2 to interact with multiple contracts across chains. It performs read-only calls to fetch token balances using `balanceOf(address)` and pool positions using the appropriate pool interface (Uniswap V2: `getReserves()`, Uniswap V3: `positions()`, Curve: `balances()`, Balancer: `getPoolTokens()`). For bridge operations, it reads the bridge contract's status via a view function before initiating transfers. Gas estimation is performed sequentially for each step using `estimateGas` on the respective contract methods, and the total is summed. The tool also tracks the user's nonce across transactions to prevent conflicts. All bridge transfers use the bridge contract's `transferTokens()` method with the destination chain ID, token address, and amount. Post-bridge, the tool calls the destination pool's `addLiquidity()` (or equivalent) with appropriate slippage parameters derived from current pool reserves. After LP tokens are minted, any leftover token dust is transferred back to the user using the destination token's `transfer()` method. All transactions are built with EIP-1559 fee data using `feeData` from the provider, ensuring optimal gas pricing.
WHAT IT CANNOT SEE
This tool cannot verify bridge contract security—it does not audit the bridge's code or its validator set. It cannot guarantee finality across chains; bridge transactions may be delayed or fail. It cannot detect bridge outages or congestion. It cannot ensure destination pool slippage protection—you must set appropriate slippage tolerance. It cannot validate off-chain liquidity depth; destination pools may have insufficient liquidity. It cannot confirm that wrapped tokens maintain their peg to the original asset. It cannot protect against bridge hacks, validator collusion, or malicious bridge operators. It cannot verify that the destination pool supports the exact token standard or has the correct fee tier. It cannot detect temporary network issues or mempool congestion that could cause transactions to drop.
PLEASE NOTE
This tool is EVM-only and supports Ethereum, Polygon, BNB Chain, Arbitrum, Optimism, and Avalanche. All transactions are signed by the connected wallet, and the user pays gas fees on both source and destination chains. The migration process involves multiple transactions across chains—ensure you have sufficient native tokens on both chains to cover gas. Always test with small amounts on testnet before migrating significant value. The bridge contract address must be trusted; verify it matches the official bridge for your chosen networks.