Skip to content
IceRootDocs
2 min read

Network status

View MarkdownAI index

Heartwood Core, the production Rust node, is still being built. A reference devnet runs now. The public testnet has not launched, and mainnet is not live.

These docs are a working specification: parameters, economics, and validator rules may change. The reference devnet and the sample data in the wallets and explorer show how things work today, not how mainnet will behave.

This page will mirror IceRoot’s release announcements. A live status feed is planned.

Release announcements

Section titled “Release announcements”

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.

Releases carry no signature from a signing key. 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. The link to the announcement channel is not published yet.

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/status reports finalizedHeight.
  • 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 status and 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.

Consensus and finality → · Validator hardening →