Skip to documentation
Resources/Docs
MigrationSinjoh v2

Migrate an existing token

Open a separately funded Sinjoh market while preserving the existing token and holders.

3 min read·
On this page

A new market; the same token

Migration opens a canonical Sinjoh market for an already deployed token. It does not replace the token contract, mint a new supply, wrap holder balances or require holders to exchange their tokens. Existing legacy pools and LP positions are not automatically imported or withdrawn.

The new market uses the market hook, a new vault and optionally a migration route. It supports ordinary Sinjoh trading charges, liquidity maintenance, treasury, yield and the optional funded floor. There is no launch surcharge, launch first-buy feature or new Sinjoh transfer gate on the unchanged token.

Immediate Safe approval, then a seeded opening

  1. A current Safe calls scheduleOpening(token, backing, creator, legacy) to approve the exact token, backing, named creator and reference pool.
  2. The named creator or a current Safe supplies the token and backing seed, with the required ERC-20 approvals.
  3. The opener supplies the current legacy price, slippage limit, deadline, token inventory’s top tick and selected market configuration.
  4. open validates the live legacy reference price, registers the market, creates its vault, initializes the pool, places the seed and creates any route/stage atomically.

Reference price and compatible seed

The approved legacy reference must identify an initialized compatible v3/v4 pool for token and backing. A token that exists only on a launch platform’s bonding curve does not thereby have an initialized graduation pool. The contract reads the reference’s live price and rejects a mismatch beyond the opener’s limit.

The token is unchanged, so its actual transfer, approval, fee-on-transfer, blocklist and destruction behavior must be compatible with the selected operations. Seed transfers must deliver the exact amounts; selecting a buyback-to-burn action requires token-compatible destruction support.

Floor funding and holder continuity

With the floor enabled, seed backing left after live-band placement becomes protected floor cash and lifts the initial floor as far as fully funded under the cap. Existing holders outside the new market remain part of the relevant obligations. With the floor off, seed surplus stays treasury.

Floor-bought migrated tokens go to the dead address rather than invoking an assumed burn function; total supply remains unchanged. Holder-reward reconstruction must include preexisting holders. Metadata reuses available legacy Sinjoh metadata while preserving on-chain name/symbol, leaving unavailable fields empty.

Opening is not automatic position importing

Users close their old positions and create new ones when appropriate; automatic v3/v4 position importing is removed from this release. This guide does not choose any particular token’s seed allocation, fee settings, floor choice or stage terms. The actual INJOH migration is a distinct configured transaction.