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

Uniswap V4 Migrator

When to use

• You are integrating Doppler's preferred migration destination (Uniswap V4).
• You need to reason about V4 standard migration vs split migration behavior.
• You are validating migrator outputs after Airlock.migrate(asset).

Prerequisites

• Confirm liquidityMigrator points to the intended V4 migrator path.
• Confirm whether split distribution is required (UniswapV4MigratorSplit).
• Confirm asset/numeraire orientation and recipient/locker settings.

Core workflow

1. Trace Airlock.migrate(asset) through initializer exit and migrator handoff.
2. Validate selected V4 migrator path:
   • UniswapV4MulticurveMigrator
   • UniswapV4MigratorSplit
3. Verify destination V4 liquidity state and recipient/locker outcomes.
4. If split mode is active, verify split recipient payout and top-up pull-up behavior.

Quick facts

Failure modes

• Misconfigured V4 migrator wiring in Airlock.
• Wrong migrator selection for expected split/non-split behavior.
• Incorrect isToken0 orientation in split configuration.
• Assuming split/top-up hooks are active without explicit split migrator setup.

References

• OVERVIEW.md
• INTERFACE.md
• VERIFICATION.md
• proceeds-split-migration
• pda-multicurve
• airlock
• verification