Skip to content
IceRoot

Use cases

Assets can outlivetheir networks.

IceRoot gives digital assets a simple, durable home under post-quantum keys, across their whole lifecycle. Each story below is built from the same standardized operations, with no smart contracts.

  1. 01Launch

    Created on IceRoot with a fixed supply.

  2. 02Stay

    Held and transferred for as long as it fits.

  3. 03Migrate in

    Carried over from another chain.

  4. 04Recover

    Rebuilt from a declared recovery point.

  5. 05Migrate out

    Leaves for an allowed destination.

Generic examples. They describe no real project, and none of this is live yet: IceRoot is in development. At launch, certified migration supports one source network, Ethereum (ERC-20 tokens); stories that start elsewhere need that network’s Connector adapter.

Building blocks

Every story uses the same operations.

No asset runs code of its own. Each path combines a few standardized protocol operations, so the rules and interfaces stay the same from one project to the next.

  • CREATECreate

    The whole supply is created once, and it is fixed.

  • TRANSFERTransfer

    Pay 1 to 256 recipients in one transfer.

  • TIME LOCKTime-locked transfer

    Vesting tranches and reserves that no one can revoke.

  • MIGRATE INCertified migration in

    A list that at least 36 of the 53 validators rebuild and sign.

  • MIGRATE OUTRecorded exit

    Units leave for a destination on the asset’s allow-list.

01 · Launch

Launch without token code.

Create a native asset with a fixed supply and give holders a standard asset from day one. Staying and moving on are both open.

01New asset

Launch a native asset

No token contract to write, deploy or audit.

A project creates its asset through Seedbed. The whole supply is created once, at creation, and no operation adds to it. It reaches initial holders in transfers of up to 256 recipients, and vesting tranches or reserves are released with time-locked transfers that no one can revoke. If IceRoot meets the project’s needs, the asset simply stays.

PlannedA distribution kit for launchpads that turns allocation lists into multi-recipient transfers, with a public proof of distribution.

Built fromCREATETRANSFERTIME LOCK

SeedbedIceRoot

Explore Seedbed
02New asset, own chain later

Launch before your own mainnet

A project can launch on IceRoot without becoming trapped on IceRoot.

The project launches its asset on IceRoot while it builds its own chain, and holders use the asset in the meantime. When the chain is ready, the project names the destination exactly, adds it to the asset’s allow-list and opens migrate-out. Holders move through recorded exits. As a compatible destination, the new chain verifies IceRoot finality, records each exit and rejects duplicates. Moving out is a success, not a failure.

Built fromCREATETRANSFERMIGRATE OUT

SeedbedIceRootProject’s own chain

02 · Preserve

Keep ownership when a network cannot.

Networks fail, retire or stop being the right home. The ownership record can continue on IceRoot, where the asset stays transferable.

03Existing asset

Retire or consolidate a chain

“We no longer need our own blockchain.”

A project that no longer wants to run its own network, or wants fewer networks to run, can keep its asset on IceRoot instead. A snapshot at a final block of the old chain becomes a migration list, validators rebuild and certify it, and holders carry on transferring. Each source asset still migrates on its own. Retiring a chain this way is a plan, not a failure.

Built fromMIGRATE INTRANSFER

Retiring chainIceRoot

04Existing asset

Keep an asset after its chain ends

The lifetime of an asset does not have to equal the lifetime of the blockchain on which it was created.

When a chain loses its developers, validators or users, its holders still own something. Where validators can independently reconstruct the source state, a certified snapshot can carry that ownership record to IceRoot. A single archive alone is not a validator-certified source. Holdings whose holders never name an IceRoot account are shown as an unissued remainder; nothing is swept to an authority, a treasury or other holders.

Built fromMIGRATE IN

End-of-life chainIceRoot

05Existing asset

Preserve a dormant asset

Long-term preservation of a whole asset.

When a project goes quiet, its asset can be preserved as a whole: balances, supply counters and provenance, recorded by a network built to agree on who owns what. Holders control their units with their own IceRoot keys, and the asset stays transferable whenever they want to use it.

Built fromMIGRATE IN

Quiet project’s chainIceRoot

06Existing asset

Recover after a security incident

Balances derived from a declared recovery point and policy.

After an incident, the source project declares a recovery point and a recovery policy. A deterministic snapshot turns them into a migration list, validators reproduce the list and certify it, and the asset continues on IceRoot. It can later move to a rebuilt chain. IceRoot does not decide whether a hack happened, which holders are legitimate or which transactions are reversed.

Built fromMIGRATE INTRANSFERMIGRATE OUT

Affected chainIceRootRebuilt chain

How recovery migrations work
07Existing asset

Continue without a company

No company is required to keep an asset going.

A community can carry an asset forward on its own. It announces on its own channels which IceRoot Asset ID is the canonical asset, and that decision is the community’s. Validators verify the migration list; IceRoot does not rule on the source project or on who speaks for it.

Built fromMIGRATE IN

Source chainIceRoot

03 · Move

Move when the project is ready.

Migration is not reserved for failing networks. Healthy projects plan moves too, into IceRoot, through it, or out of it.

08Existing asset

Leave a smart contract

Replace an ERC-20 contract or proxy with a standardized asset.

A project whose token lives in a contract, perhaps behind an upgradeable proxy, can move it to a standardized IceRoot asset: no contract code, no proxy and no admin upgrade path. It is a planned reduction of attack surface, not an emergency. Ethereum (ERC-20 tokens) is the source network supported for certified migration at launch.

Built fromMIGRATE IN

Token contractIceRoot

09Existing asset

Move to post-quantum keys early

For assets meant to last decades.

Some projects prefer to move to post-quantum keys on their own schedule, well before the transition becomes urgent. Every signature verified in IceRoot consensus is ML-DSA-65, so a migrated asset is held under post-quantum keys from the moment it is credited. Its history before arrival keeps the security of its source chain. A classical source such as Ethereum has a cut-off fixed in advance that can only move earlier. Burns must fall at or before its source cut-off block, and snapshot lists must be certified before its IceRoot cut-off height. Post-quantum sources have no such cut-off.

Built fromMIGRATE IN

Source chainIceRoot

10Existing asset

Plan a project migration

Healthy projects move too.

A project can move from its chain to IceRoot and stay, or pass through IceRoot on the way to another chain. Each step uses the same certified lists and recorded exits, so the ownership record carries forward from one network to the next.

Built fromMIGRATE INMIGRATE OUT

Chain AIceRootChain B

11Existing asset

A home while you rebuild

Version 1 comes to IceRoot. Version 2 is where it goes next.

A project replacing its chain moves the asset to IceRoot while version 2 is built, and holders keep transferring it. When version 2 is ready, it goes on the asset’s allow-list, migrate-out opens and holders move on through recorded exits.

Built fromMIGRATE INTRANSFERMIGRATE OUT

Chain v1IceRootChain v2

04 · Limits

What IceRoot does not do.

IceRoot is a deliberately minimal ledger for ownership and migration. These limits are part of the design.

  • Merging assetsNot supported

    Restructuring or mergers, such as turning ABC and XYZ into NEW, are not supported. Each IceRoot asset maps to one source asset, and each source asset migrates on its own.

  • Judging a projectNot IceRoot’s role

    IceRoot provides the tools and verifies; projects decide. It does not judge which party represents a project, which block is legitimate or which balances are deserved.

  • Preventing every scamNot claimed

    Standardized assets remove arbitrary token code, not bad actors. A project can still mislead its holders, manipulate markets or abandon its work.

  • Returning to the same Asset IDNew asset

    A copy of an asset that comes back from another chain by migration registers as a new asset with its own Asset ID.

  • Every source network at launchOne at launch

    At launch, certified migration supports one source network, Ethereum (ERC-20 tokens). Other networks can be added later, each through its own Connector adapter.

Launch. Preserve. Move.

Start with Seedbed, see how certified migration works, or compare IceRoot with ERC-20 and SPL tokens.

Explore SeedbedHow migration worksCompare token models