Network status
Heartwood Core, the Rust node, is available in the public repository. A public lab devnet runs Heartwood relays and forgers, with a reference API node. Anyone can run a devnet node. The lab has no value, may reset or shut down at any time, and requires fresh test keys and passphrases. Running a relay is not validating; validators apply separately.
The public testnet has not launched, and mainnet is not live. The lab uses classical signatures and reference-compatible formats, without deterministic finality. The first public testnet is planned to open once finality is live, with provisional values and later features added through upgrades, followed by a clean genesis with the final mainnet values. No opening date is set.
These docs are a working specification: parameters, economics, and validator rules may change. The lab devnet tests the current implementation; it does not implement all of the proposed mainnet rules. Wallet sample walkthroughs remain demonstrations.
This page will mirror IceRoot’s release announcements. A live status feed is planned.
Release announcements
Section titled “Release announcements”The primary channel is the announcements channel of the IceRoot Discord. Validator applications also go through Discord; see How to apply.
Application and announcement invite: join the IceRoot Discord.
Under the draft protocol, the IceRoot team is the release authority. A release is code published on GitHub under the iceroot-network organization, and validators are instructed to install it through the project’s announcement channel, which the whitepaper names. X, this page, the IceRoot blog on iceroot.com, and the IceRoot Telegram channel mirror each announcement.
An announcement names:
- the release and whether it changes block or transaction validity;
- every activation height it contains, each on a round start;
- the SHA-256 checksum of every download.
Node and wallet releases carry no signature from a project signing key. The SHA-256 checksum of every wallet installer appears in the GitHub release notes and in the announcement channel. Apple and Windows code signing meet operating-system installation requirements. Before installing, compare the checksum in the GitHub release notes with the one in the announcement channel. Reproducible builds, which let anyone rebuild a release tag and get the same binary, are required before mainnet launches. Mirrors, including this page, repeat announcements; check checksums against the release notes and the announcement channel themselves.
Announcements
Section titled “Announcements”No network release has been announced yet. Announcements will be listed here, newest first, with dates in UTC.
Live status
Section titled “Live status”Under the draft protocol, the node API reports these signals. They describe the planned network, not the current reference devnet:
- Finality. Every block and transaction carries
finalized, and/node/statusreportsfinalizedHeight. - Stalls. After 4 rounds without a newly finalized block, about 28 minutes, nodes raise an alert and the API reports “stalled”. Production and transactions continue.
- Paused user transactions. After 24 rounds without new finality, about 2.8 hours, blocks carry only evidence, validator system messages, and the claims and refunds of hash time-locked transfers. Both levels lift automatically when finality resumes.
- Readiness. Before an activation height,
heartwood relay statusand the node API show how many active validators run a version that satisfies the new release. The count comes from what each validator’s own software reports, so it is an operational signal, not proof.