Development milestones, current availability and the work that comes next.
Current status
Development and security status
Heartwood Core, the production Rust node, is still being built. Its relay and forger already run in development builds, on development networks only. A reference devnet runs now. The public testnet has not launched, and mainnet ROOT and migration services are not live. Previews on this site run locally in your browser.
Release and review status is recorded here as work progresses.
Heartwood Core
In development · relay and forger in testing
Reference devnet
Running
Public testnet
Not launched
Mainnet
Not launched
ROOT
Not live
Seedbed
Local preview
Migration routes
None live
Post-quantum signatures
Specified · not yet built
Audits
None published
Explorer · scan.iceroot.com
Preview · sample data
Security contact
GitHub private reporting
Order of work
Baseline first. Changes one at a time.
Each stage starts when the previous one passes its gate. There are no calendar dates.
S1 · NowIn development
Faithful Rust port
Heartwood Core recreates the reference implementation, Solar Core, in Rust, keeping its classical cryptography for now, and is tested against it byte for byte. This is the first stage, and the current one. In development builds, the Rust node’s relay follows a reference network, takes blocks and transactions from its peers and serves the node API, and a forger runs beside it as its own process. The commands to run and supervise them, the recovery commands (snapshot rollback, pool clear and state clear) and a local devnet of Heartwood nodes are included. The indexer and the other operator commands are not included yet.
Next, in orderPlanned
From hardening to mainnet
Each stage gets its own specification, review and tests, and is introduced separately.
Hardening. An adversarial test campaign: floods, malicious validators, malformed data, network attacks, operator faults and upgrade drills, with benchmarks against the reference.HARDEN
Post-quantum signatures. ML-DSA-65 replaces classical signatures through a milestone, with new transaction and block formats. The test campaign runs again.PQ
IceRoot genesis. A fresh genesis, post-quantum only, with the network’s own identity: ROOT, ice and tice addresses and multi-asset accounts.ID
Finality. Lisk-BFT finality with votes carried in block headers. A block with 36 of 53 implied precommits is final and is never reverted on any synced node. The first public testnet opens once finality is live, with provisional values; asset creation, migration and Connectors follow through upgrades.FIN
Asset creation. Native assets with a fixed supply through Seedbed, atomic swaps, hash time-locked transfers and time-locked transfers for vesting.AC
Migration. Certified migration in and out, with Ethereum (ERC-20 tokens) as the source network at launch.MIG
Connectors. The IceRoot Connector that every validator runs, its adapters for source networks, and the Snapshot Builder, planned tooling with which projects will build migration lists from the same code.CON
Testnet relaunch. Onboarding validator operators toward a full set of 53, the external audits and an independent BFT review, and at least 8 weeks with finality enforced. It is relaunched from a clean genesis with the final values. Validators, testers and builders earn shares of a 10,000,000 ROOT participation pool, credited at mainnet genesis; the team handles participation case by case and the split is not decided.TESTNET
Mainnet. 53 validators selected from the public testnet, one per declared operator, every feature active from height 1, and no votes in the genesis block.MAINNET
Protocol priorities
The planned design, and what is still open.
Accounts and consensus
The working specification describes the planned design: ML-DSA-65 for every signature in consensus from block 1, 53 validators in 8-second slots, and finality at 36 of 53, at least 71 blocks after a block is produced. Values such as the finality vote window, the jail length and the multisig key cap are still open.
Assets and migration
Every native asset has a fixed supply; there is no minting. Migration lists need 36 of 53 validators and stay under a lifetime cap per asset, with Ethereum (ERC-20 tokens) the only source network at launch, registered as classical with a cut-off that only ever moves earlier. The base fee, the asset and migration surcharges, the value of Ethereum’s first cut-off and the block and transaction size limits are still open.
Releases and integrations
No release or public network API endpoint has been announced, and the public testnet has not launched. A development build guide is published for contributors who already have source access. Releases will be code on GitHub, announced with their SHA-256 checksums in the announcements channel of the IceRoot Discord and mirrored on X, the status page, the blog and Telegram. IceRoot gets its own wallets first; integration into the Monolythium wallet comes later. No destination compatibility, live migration route or exchange listing is confirmed.
ROOT and security review
ROOT is not live, and there is no token sale. The genesis block will issue 100,000,000 ROOT in seven labeled pools, blocks pay 1.8 to 2.2 ROOT by rank, and 90% of every fee is burned. The external audits take place during the public testnet. No audit is published. Vulnerabilities are reported privately through the GitHub reporting form under the published security policy, and a bounty program with a provisional reward table is public. An email address will be added once its inbox is monitored every working day.
Interactive examples across this site run in your browser with sample data. They create no assets, sign no transactions and contact no blockchain.
