GAMADocs

Launchpad

Migration

A migration moves a graduated launch's locked liquidity from its pool into a new pool on another approved trading venue, in a single step.

Why it exists

GAMA runs its own copy of the Uniswap V4 trading software. Migration lets a launch's liquidity move to another compatible Uniswap V4 deployment later, for example an official one on GIWA. No official deployment on GIWA has been approved. The existence of one would not be enough on its own. It must first be shown to be compatible.

Who can migrate

Only the protocol owner can migrate a launch, and only to a venue the protocol owner has approved. Approving venues is a trust decision by the owner. See Administration and trust.

How it works

Everything happens in one transaction. If any part fails, nothing changes.

  1. The locked liquidity is taken out of the old pool.
  2. A new pool is opened on the new venue at exactly the old pool's price.
  3. The liquidity goes into the new pool and is locked again straight away.
  4. The launch's fees carry over unchanged.
  5. Any small leftovers go to the protocol treasury.

The price cannot change during the move. The new position never holds more liquidity than the old one.

After a migration

The old pool stays open with its original fees. Liquidity other people added there stays there. Reward-mode launches keep earning holder rewards from trades in the old pool too. See Holder rewards.

A launch cannot move back into a pool it has used before.

On a venue run by someone else, that venue's own protocol fee settings apply, and those fees are not GAMA revenue.

GAMA is deployed on GIWA Sepolia testnet only. Nothing in this documentation is an offer or financial advice.