Skip to content
IceRootDocs

Heartwood Core

Heartwood Core is IceRoot’s Rust node implementation, tested against a pinned Solar reference.

The production node is still being built. A public lab devnet runs now; the public testnet and mainnet have not launched. The Heartwood Core repository is public. The lab has no value and may reset at any time; run a devnet node to follow it. These docs are a working specification: parameters, economics, and validator rules may change. See Network status for updates.

The development workspace contains:

  • heartwood-crypto: keys, signatures, transaction and block codecs.
  • Milestone handling: network rules selected by height.
  • State and transactions: account state, rounds, transaction handlers, and block application and reversal.
  • Storage and pool: SQLite persistence, restart and replay paths, and transaction admission.
  • Peer wire codec: reference-compatible message encoding.
  • Differential tests: committed vectors, generated cases, and block-sequence replay against reference behavior.
  • Peer client: sessions with reference peers over WebSocket.
  • Node API: the reference’s block, node, peer, transaction and wallet routes, served by the node.
  • Peer-to-peer server: takes blocks and transactions from peers and serves the relay’s forger, with the reference’s rules and some limits of its own.
  • Forger: holds the delegates’ keys and forges through its relays, with a signing record.
  • Commands and devnet: heartwood relay and heartwood forger with run, start, stop, restart, status and log; network generate; and a local devnet of Heartwood nodes.
  • Recovery commands: snapshot rollback, pool clear and state clear, also available with colon aliases.
  • Diagnostics: heartwood doctor runs deterministic checks and exports a redacted report.
  • Node configuration: the reference’s configuration files, read for the chosen network and token.

A relay and a forger are included, each its own process. The relay follows a reference network, applies blocks, keeps a transaction pool, takes blocks and transactions from its peers and serves the node API. Start it with heartwood relay run, as described in Build from source. heartwood devnet starts a local network of Heartwood relays and forgers on one machine. The indexer, the remaining operator commands and the network features planned for mainnet are not included yet.

Development adds native assets, migrations, post-quantum authentication, and deterministic finality in stages. The draft whitepaper proposes that all four are active from mainnet’s first block. Runnable commands in these docs refer to the current source.

  • Accounts hold balances and authorize actions.
  • Transactions describe changes to those accounts or to network records.
  • Blocks put accepted transactions into an ordered history.
  • Validators validate transactions and blocks according to the network’s rules.
  • Native assets keep their identity and accounting inside the protocol.

ROOT pays network fees and provides the basis for validator voting and rewards. Use the asset’s identity when integrating it.