Skip to main content
A community running a coin on another platform can move it to Archr. A migration launches a fresh coin with Archr’s burned launch liquidity, airdrops most of the new supply to the source coin’s existing holders, records the community’s lead as creator, and disables the ticker so nobody can launch over the name. Migration is the one launch path that is not self-serve: requests are evaluated by the team. That is a judgment call about whether a community is real; there is no permissionless way to trigger a migration. Only external coins can migrate: a coin already launched on Archr cannot.

​
What a migration launch does

On approval, a single transaction:
  1. Deploys a fresh coin (fixed 1,000,000,000 supply, same shape as every Archr coin).
  2. Escrows 2% of the supply for ARCHR holder rewards.
  3. Allocates the source-holder pot, up to 70% of the supply (sizing below).
  4. Records the community’s lead as the coin’s creator, so 1% of trading volume routes to them as ETH, enforced by the contract.
  5. Disables the coin’s ticker immediately, in the same transaction; no 14-day window applies on this path.
  6. Places the remaining supply, at least 28%, as the single-sided sell wall, with the launch-wall LP burned to the dead address. The launch FDV target scales with the pot, up to about $30,000, so pool liquidity depth matches other launches.

​
How the pot is sized

The source-holder pot is the smaller of:
  • 80% of the source coin’s supply held outside its own LP, and
  • 70% of the new coin’s supply.
The out-of-LP measurement is taken at a snapshot block, and both the block and the measurement are published before the migration executes. This sizing is team-attested: the team publishes what it measured and the pot is set from that number, so anyone can recompute the figure from the snapshot block, but the measurement itself is not made by a contract. The 80% haircut ties the pot to the supply the community actually holds; tokens sitting in the source coin’s own pool do not count toward it.

​
How holders are paid

Source holders receive the pot pro-rata, immediately after launch: holding twice as much of the source coin at the snapshot block means receiving twice the share of the new coin. The recipient list is computed off-chain by the platform from the published snapshot block, and the payout is batched on-chain transfers, all visible on Blockscout. There is no claim step; tokens arrive at the same addresses that held the source coin.

​
The escrow

The migration escrow is 2% (against 5% on other launches) and pays ARCHR holders in three tranches at 24h, 72h, and 168h after launch. There is no early-adopter bonus on migrations: the early-buyer pot exists to reward first buyers of a brand-new coin, and a migrated coin arrives with its holder base already in place. Tranche amounts and unlock times are fixed at launch and enforced by the escrow contract; see holder rewards for eligibility.

​
One migration per source

A source coin can migrate once, ever. This is enforced on-chain: a second migration attempt against the same source reverts, regardless of who requests it or who approves it.

​
Requesting a migration

There is no form and no on-chain request path. Reach out to the team via @archrdeploy. Approval is discretionary and evaluated by the team.