Token Migration Bridge with Ratio Conversion
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
Token Migration Bridge with Ratio Conversion enables seamless token swaps from an old contract to a new one at a specified conversion rate. It reads your old token balance, checks the migration contract's status and current conversion rate, then handles the entire migration workflow: approving the migration contract to spend your old tokens, executing the migration call, and optionally sending the new tokens to a different destination address. The tool supports custom ratios (e.g., 1:0.5, 1:10) and allows you to migrate a partial amount or your full balance.
This tool is essential for projects undergoing token upgrades, mergers, or rebases where holders need to exchange legacy tokens for a new version with a predetermined conversion rate. It eliminates manual approval-and-swap steps, reducing user error and gas costs by consolidating into two transactions (approval + migration) with clear progress visibility.
HOW TO USE
1. Connect your EVM wallet to the network where the old token and migration contract are deployed.
2. Enter the old token address, new token address, and the migration contract address.
3. Specify the conversion ratio in the format "1:0.5" (meaning 1 old token = 0.5 new tokens) or "1:10" (1 old = 10 new).
4. Optionally set the amount to migrate—leave empty to migrate your full balance.
5. Optionally specify a destination address—defaults to your connected wallet.
6. Click "Check Balance & Rate" to read your balance, the migration contract's active rate (if available), and your current allowance.
7. Review the summary showing your balance, the conversion rate, and the amount of new tokens you will receive.
8. Click "Execute Migration" to approve the migration contract and perform the swap. Progress is shown with a step-by-step status bar.
TECHNICAL MECHANISM
The tool uses a two-transaction sequence to ensure safety and atomicity. First, it calls approve(spender, amount) on the old token contract to grant the migration contract permission to spend the specified amount. The approval uses gas estimation with a 20% buffer to handle network variability. Once the approval is confirmed, the tool calls migrate(amount, recipient) on the migration contract. The migration contract is expected to burn or lock the old tokens and mint or transfer the new tokens at the configured ratio. The tool reads token decimals for both contracts to format amounts correctly using ethers.utils.parseUnits and formatUnits. Gas costs are calculated from the receipt's effectiveGasPrice, reflecting actual post-EIP-1559 fees. If the migration contract provides a getConversionRate() view function, the tool reads and displays the on-chain rate instead of relying solely on the user-provided ratio, ensuring transparency.
WHAT IT CANNOT SEE
This tool cannot verify the security or legitimacy of the migration contract or the new token—malicious contracts could steal funds or mint unlimited tokens. It cannot ensure the migration rate will not change after the transaction; the contract owner could modify the rate between your check and execution. It cannot recover tokens if the migration contract is malicious, compromised, or has a bug that locks funds. It cannot migrate tokens that are staked, locked, or deposited in other protocols—only tokens held directly in your wallet. It cannot prove that the new token will have liquidity or value post-migration; the new token may lack exchange support or market demand. Users must independently research the migration project and contract code before proceeding.
PLEASE NOTE
EVM chains only. This tool works with any ERC-20 token and migration contract that follows the standard approve/migrate pattern. Always verify the migration contract address from official project sources—phishing contracts are common during token migrations. Test with a small amount first on testnet or mainnet before migrating large balances. The tool does not handle rebasing or fee-on-transfer tokens; use only with standard ERC-20s.