Relaunch Tool — One-Pool Migrations on Liquid
2026-05-01 — #launch#protocol#migration
What's new
/relaunch is live. Anyone can relaunch a token they hold or deploy a successor pool for a community whose original token has gone stale — without trusting the team or any intermediary.
The flow is 100% user-signed:
- Sign deployToken — the new Liquid token is yours from the first block.
- Sign pool creation — CREATE2-deterministic, ratio locked in at this step.
- Sign setNewToken — wires the migrator to your fresh pool.
Then anyone holding the old token can deposit it on /relaunch?tab=redeem and receive the new token at a fixed newOut = (oldIn × ratio) / 1e18. Old tokens go to 0xdead. No expiry, no sweep.
What the platform does and does not do
Does: record the migration row, surface it in the directory at /relaunch, serve /redeem and /by-old reads against the on-chain pool.
Does not: custody funds, sign transactions on your behalf, or gate deployment. Every byte on-chain came from your wallet.
Spam gates
To keep the directory readable:
- 5 launches per OLD per 24h (per-deployer)
- 30-day Transfer activity gate — the OLD must have moved within the last 30 days
- Optional verified-creator EIP-712 sig if you held an admin role on the OLD (more on that here)
Configurable allocation
Every relaunch carries an allocation percentage — the share of the new token's supply set aside for old holders to redeem. Defaults to 20%, configurable per launch from 1% to 90%.
- At least 50% triggers a warning (you're giving away half the supply)
- Below 1% or above 90% blocks the launch outright