Skip to content
IceRootDocs

Protocol design

The whitepaper is a working specification of the intended mainnet: parameters, economics, and validator rules may change. This page maps its proposals to the current implementation.

Heartwood Core, the production Rust node, is still being built. A reference devnet runs now; the public testnet has not launched. See Network status for updates.

The network records ownership through standardized accounts, assets, and transactions. The draft excludes a virtual machine and user-deployed executable code. Wallet interfaces, metadata hosting, prices, the explorer, and external-chain Connectors stay outside consensus.

Its four main proposals are:

  • Post-quantum authentication: ML-DSA-65 for native protocol signatures from mainnet genesis.
  • Deterministic finality: header-carried votes establish a finalized history.
  • Native assets: canonical AssetIDs, a fixed supply for every native asset, and explicit supply accounting.
  • Certified migration: manifests rebuilt and attested by a validator quorum, permanent provenance, and lifetime issuance caps.

The draft proposes all these features from mainnet height 1, together with atomic swaps, hash time-locked transfers, non-revocable time-locked transfers for vesting, account names, and validator reward-sharing declarations. The development sequence used to build them is separate from that launch specification.

AreaCurrent implementationDraft mainnet design
Core signaturesBIP340 compatibility baselineML-DSA-65
AddressesBase58Check with a network byteBech32m, ice1… on mainnet and tice1… on the public testnet
Portal identityVersion-90 devnet addressSeparate from the eventual mainnet identity format
Transaction IDHash of serialized bytes including signaturesDomain-tagged hash excluding signature witnesses
Vote contentsAt most 1,024 bytesAt most 1,280 bytes, naming 20 to 53 validators with at most 5% each
Node runtimeCrypto, state, storage, pool, and wire components under development, plus a relay with its peer-to-peer server, a forger and the process commands, for development networks; indexer not included yetSeparate relay, validator signing process, and indexer
Application dataDesktop devnet integration; wallet sample walkthroughs and live public lab explorerLive node and indexer records

Use the current source when integrating an application. The browser wallet provider already works as the draft specifies: it runs only on IceRoot’s own sites and on sites the holder adds, the holder approves every connection and message signature, and it never signs transactions.

ROOT voting selects validators. The draft constrains how voting weight can be concentrated, rate-limits election-driven changes to the validator set, and provides tools for identifying observable concentration. These measures deliberately add friction for concentrated actors without attempting to solve real-world identity or to prevent one entity from operating several validator identities. Validators and voting describes each rule.

The draft routes protocol changes through published releases with named activation heights and preserves finalized history. Releases are announced in the announcements channel of the IceRoot Discord, and X, the status page on docs.iceroot.com, the IceRoot blog, and the IceRoot Telegram channel mirror each announcement.

The protocol is meant to be feature-complete at mainnet, with no feature roadmap after launch. About IceRoot describes what later releases can change.

The draft also separates fees from rewards:

  • Fees: ROOT pays every transaction fee. Each fee, surcharges included, is 90% burned and 10% paid to the forging validator.
  • Rewards: block rewards add issuance. Each reward pays 5% to the Development fund and 5% to the Ecosystem fund, and the remainder to the forging validator.
  • Accounts: the team account, the genesis pool accounts, and both funds are 2-of-3 native multisig accounts, labeled on the explorer.

The genesis block issues 100,000,000 ROOT in seven labeled pools, and IceRoot holds no token sale. After genesis, ROOT’s supply grows only through block rewards. Assets created through Seedbed have a fixed supply; external assets receive units only through certified migration lists under their lifetime caps. ROOT supply and distribution describes the pools, the on-chain lock of the team allocation, and fee grants.

The whitepaper leaves explicit TBD items:

  • Genesis identifiers, and the addresses of the pool accounts and the funds.
  • The base fee rate and the fees of asset, migration, swap, and time-locked operations.
  • Capacity limits and the implied-vote window.
  • Penalty durations and parts of migration operation.
  • Audit scopes, reviewers, and reports.

Its present-tense descriptions do not establish a deployment or completed audit. Keep unresolved values open until a release specifies them.

Consensus and finality → · Native assets → · Migration →