Skip to content
IceRoot

Post-quantum asset continuity

Build on ice.Root when you’re ready.

A simple, durable home for digital assets under post-quantum keys. Launch without smart contracts, keep ownership when a network fails or retires, and move on when the project is ready.

Follow the asset.

ASSETSEEDBEDICEROOTNEXT NETWORKTHE NETWORK CHANGES. THE RECORD CONTINUES.
Ownership in motion.

Transfers and distributions become part of the asset record.

How IceRoot is used

Launch. Preserve. Move.

Post-quantum signatures are the security foundation. Asset continuity is the product: an asset can launch here, stay, arrive from another chain, recover and later move on, with no smart contracts.

01 · LaunchSeedbed

Launch a native asset.

Set a name and a fixed supply, created once. Distribute it in transfers of up to 256 recipients, with vesting through time-locked transfers. There is no token contract to write.

SeedbedIceRoot

Explore Seedbed
02 · PreserveCertified migration

Keep the ownership record.

When a network fails, retires or no longer fits, its asset can continue here. At least 36 of the 53 validators rebuild and sign each migration list, and a lifetime cap bounds what migration can credit.

Original networkIceRoot

How migration works
03 · MoveRecorded exit

Move on when ready.

An asset can leave for a destination on its allow-list, including a project’s own chain, and the exit is recorded. Moving on is a success, not a failure.

IceRootNext network

Explore use cases

Why not just launch an ERC-20 or an SPL token?

You absolutely can.

ERC-20 and SPL are excellent if those ecosystems are your destination. IceRoot is built for asset continuity: before, during, between and after other blockchains.

The native asset experience

The whole asset, in one record.

Inspect origin, supply, transfers and migration history by Asset ID.

The ticker is not the identity.

Symbols can repeat. The Asset ID identifies the asset; its origin and supply explain what you hold.

EXTExample Token, migrated from EthereumEXAMPLE-ASSET-ID-7F3A-91C2
EXTAn unrelated asset also called “EXT”EXAMPLE-ASSET-ID-D93B-44E0

Same symbol. Different assets. Check the Asset ID.

Example asset record

Asset record

Example Token

Migrating in

EXT
Asset ID
EXAMPLE-ASSET-ID-7F3A-91C2
Current network
IceRoot Network
Origin
Ethereum (ERC-20) · burn-events example
Supply
Certified migration · lifetime cap of 10,000,000 EXT · 18 decimals
Migration
Destination: unassigned

Lifecycle label · sample display state

  1. Rooted
  2. Retired
  3. Rooting
  4. Migrating in
  5. Seeded
  6. Active

Migrating in: A migrated asset that still accepts new inbound lists. Burn-event routes stay in this state while the asset keeps accepting them.

One label applies at a time, and it can change as the asset’s records change. A label is not consensus state and never freezes transfers. The label names are a draft. Lifecycle labels

Transfer and distribution activity

  1. #0003Transferexample-account:ava-0102 → example-account:dev-11880.75
  2. #0002Transfer12 recipients in one transfer6.00
  3. #0001Migrated inCertified list of burn events on Ethereum250.00

Native capabilities

The essentials, built in.

Asset operations follow shared protocol rules. Every project uses the same transaction types.

  1. 01

    Simple native assets

    Created with a fixed supply by a protocol operation, without token code.

  2. 02

    Transfers between accounts

    Pay 1 to 256 recipients in one transfer, with one memo of up to 255 bytes.

  3. 03

    Atomic swaps

    Two assets change hands in one all-or-nothing transaction. Matching stays off-chain.

  4. 04

    Time-locked transfers

    Vesting tranches that unlock on schedule and that no one can revoke.

  5. 05

    Post-quantum accounts

    ML-DSA-65 for every signature in consensus, from the first block.

  6. 06

    Migration records

    Source, method and destination recorded with the asset.

What IceRoot is not

No EVM. No DeFi. No user-deployed contracts. No freeze or clawback scripting.

No arbitrary compliance logic, no stablecoin or real-world-asset platform and no application runtime. Leaving these out is part of the security model: IceRoot is a deliberately boring ledger for ownership and migration.

Heartwood Core

Rust at the core.

Heartwood Core separates peer networking, transaction processing and block validation into clear modules.

Operators run the relay and the forger as separate processes, with scheduled rounds, voting and a consistent API.

Heartwood Core · RustConceptual view
ProcessRelay
Network and state
ProcessForger
Signs blocks in its slot
In the coreNative protocol modules
  • Accounts
  • Assets
  • Transfers
  • Voting
  • Rewards
  • Migrations
Relay and forger run as separate processes, so validator keys stay out of the process that faces the network. Protocol modules are native code in Heartwood Core, not programs uploaded by users.

Scope

Security has boundaries.

Post-quantum signatures and native accounting protect the IceRoot side. A migrated asset also depends on its source network and the route that carried it.

Read the security scope
Per asset · stated in its trust labelOutside IceRoot
  • Source chain
  • List certification
  • Custody gateways
  • Destination
Inside IceRoot
  • PQ account authentication
  • Validator signatures
  • Consensus
For a migrated asset, both boxes apply. IceRoot’s protection does not extend to what sits outside it.

Product family

Four parts, each with one job.

  • Heartwood Core

    The Rust implementation of IceRoot Network: relay, forger, indexer and native protocol modules.

  • Seedbed

    Asset creation and batch distribution for project teams.

  • IceRoot Connector

    The framework for integrating a specific external network as a supported migration route.

  • Explorer

    A visual record of assets, transactions, blocks and validator activity.

YOUR NEXT STEP

Make yourself at home.

Get started
Get a walletDesktop, browser, or mobileExplore the networkExplorer and validator proposalsJoin the communityGitHub, Discord, and Telegram