Migrations and continuity
The draft whitepaper describes assets arriving through certified source records and leaving through recorded exits. Assets stay transferable while hosted on IceRoot.
For step-by-step guidance, read the migration guide. It covers migrating in, planned chain retirement, end-of-life chains, leaving a smart contract, recovery after an incident, a temporary home while rebuilding, and migrating out.
Two starting points
Section titled “Two starting points”Seedbed is the native asset creation and distribution experience. It describes an asset and its initial allocation without deploying a token contract. A Seedbed asset has a fixed supply, and vesting schedules use time-locked transfers.
An external migration starts from an existing network. Its records must connect the source asset and source event to an IceRoot asset and receiving account.
Proposed inbound flow
Section titled “Proposed inbound flow”- Register the source network and asset, with a fixed lifetime issuance cap and an explicit trust model.
- Publish a manifest that maps source holdings to receiving IceRoot accounts.
- At least 36 of the 53 validators separately rebuild and attest to the manifest using their own Connectors. Each validator reads the source chain through its own node or a publicly declared provider. The limit of 17 validators per provider is a declared policy shown on the explorer, not a consensus rule.
- Submit the certified lines in order, in chunks of up to 256. Recipients are fixed before certification.
At mainnet launch, the draft supports one source network: Ethereum (ERC-20 tokens). Each further network needs its own Connector adapter and registration by the validator quorum; Connector adapters describes how to propose one.
The draft supports snapshots and source-chain burn events. A certified manifest is creditable immediately:
- Before its first credit: the quorum can cancel it.
- After its first credit: a mistake requires correction using existing units.
There is no optimistic credit or pending state inside the proposed consensus model.
Source network class and cut-off
Section titled “Source network class and cut-off”Registering a source network also records its class: post-quantum only if both the holders’ ownership signatures and the chain’s finality are post-quantum, and classical otherwise. Ethereum, the network supported at launch, is classical: it authenticates ownership with ECDSA signatures and finality with BLS signatures.
A classical source network also gets a cut-off: an IceRoot height and the matching source block. The validator quorum fixes it when it registers the network, before any of the network’s lists is certified. Afterwards, a quorum-certified update can move it earlier at any time, never later. When to move it is a validator policy, not a consensus rule: the quorum moves it earlier at once on credible public evidence of a quantum computer able to break the network’s signatures, or of a practical attack on them. A post-quantum source network has no cut-off. Ethereum’s first cut-off value is fixed before mainnet; see the parameter table in the whitepaper.
After a classical source network’s cut-off, consensus refuses a new external asset registration from that network, an event list whose source range reaches past the cut-off block, any snapshot list, whatever its snapshot block (its accounts are bound with proofs made with the network’s classical keys), and any late binding, whose deadline must fall at or below the cut-off. A list certified before the cut-off keeps being credited afterwards, because its accounts were fixed before certification. An event list whose whole range lies at or before the cut-off block can still be certified after the cut-off, because each of its burns named its IceRoot account in a transaction the source chain finalized before it.
Once a signature scheme can be forged, a new proof made with it no longer shows who owned what, while proofs and snapshots made before that point stay valid. Nobody can know that moment in advance, so the cut-off is fixed ahead of time and only ever moves earlier.
What a route must explain
Section titled “What a route must explain”| Question | Why it matters |
|---|---|
| Which source event is accepted? | Identifies the evidence for a transfer |
| What establishes source finality? | Determines when the source record is usable |
| Who verifies or authorizes it? | Makes the trust model explicit |
| What prevents reuse? | Prevents the same source event crediting twice |
| What happens on failure? | Defines retries, cancellation, or recovery |
| Which destination accepts it? | Connects outgoing records to their intended network |
Each route must name its trust assumptions. A custody gateway holds existing units on behalf of users; its operator has a different role from a validator-certified migration. See Custody gateways.
Hash time-locked transfers support swaps with other chains, but they complement migration rather than replace it. A swap moves units that already exist on each chain; it never creates units of a migrated asset or counts as a migration credit.
Exits and their limits
Section titled “Exits and their limits”In the draft, MIGRATE_OUT destroys units on IceRoot and records an allowed destination, destination account, and unique exit ID. The destination must verify and honor that record. IceRoot cannot force it to credit the user, and the proposed exit has no refund.
The record has three important limits:
- Burned and migrated out remain separate counters.
- Source-to-destination account links are public and permanent.
- The lifetime cap bounds a compromised certification quorum; there is no additional issuance delay or rate limit.
The destination registry also records each destination’s class and, for a classical destination, its cut-off, using the same test as for a source network. Wallets and the explorer warn before a migrate-out to a classical destination past its cut-off, and before a hash time-locked swap whose other side is a classical chain past its cut-off. Consensus does not refuse either: the warning is for the holder to weigh, not a rule that blocks the exit or the swap.
The live explorer has no migration records or routes on the public lab devnet. It does not display the proposed asset lifecycle labels. The proposed consensus keeps two lifecycle flags per asset. Descriptive labels are separate from consensus state; see Lifecycle labels.
Who decides
Section titled “Who decides”IceRoot provides the tools and verifies; projects decide. Projects announce on their own channels which AssetID is their canonical asset, and the verified-asset list reflects those announcements. A validator certification means that a list was reproduced from its declared inputs, not that the migration is endorsed. Each IceRoot asset maps to one source asset, so merging several source assets into one is not supported.