Source References: Use Doppler deployments as the contract source of truth for deployed addresses and revisions.

Uniswap V2 Migrator

When to use

• You are integrating a legacy migration destination based on Uniswap V2 pools.
• You need to verify Airlock-to-migrator handoff behavior for the V2 path.
• You are auditing compatibility behavior on networks where V4 migration is not used.

Prerequisites

• Confirm liquidityMigrator is configured to the V2 migrator implementation.
• Confirm migration policy allows V2 for this launch.
• Confirm asset/numeraire token ordering and destination recipient assumptions.

Core workflow

1. Trace Airlock.migrate(asset) up to migrator handoff.
2. Verify post-fee balances sent by Airlock to the V2 migrator path.
3. Verify V2 destination liquidity state after migration.
4. Validate recipient/locker ownership of migrated liquidity.

Quick facts

Failure modes

• Wrong liquidityMigrator wiring for a V2 target.
• Migrating to V2 when a preferred V4 path is available for the same launch policy.
• Token orientation mismatch between Airlock output and destination pool assumptions.
• Assuming V4-only features (split/top-up hooks) exist on the V2 path.

References

• OVERVIEW.md
• INTERFACE.md
• VERIFICATION.md
• liquidity-migration
• airlock
• verification