Node operation

Run headless with wildrootd or run the desktop application's integrated node.

The daemon is the server-oriented node. The desktop application links the full WildRoot node into the same process and does not spawn wildrootd as a child.

Daemon

wildrootd

Standalone headless node exposing Integration RPC, Ethereum JSON-RPC, Stratum and Explorer services for server deployments.

Desktop

wildroot-gui

Standalone graphical application with a full in-process WildRoot node, wallets, peer information, explorer views and mining controls.

CLI

wildroot-cli

Standalone JSON-RPC client for querying and controlling a running daemon or compatible integration endpoint.

Runtime configuration

Operational settings persist under the node data directory.

state/settings.toml contains documented runtime options for listener addresses, file logging, log level/retention, P2P connection limits, Integration RPC limits, Stratum client limits, EVM HTTP/WS client and subscription limits, and Explorer concurrency.

The GUI stores interface preferences separately in state/gui-settings.json. The compressed binary peer address book lives in state/peers.bin.

Persistent data layout

ledger/
state/
  settings.toml
  gui-settings.json
  peers.bin
dag/
contracts/
indexes/
wallets/
logs/

Headless

Start the daemon.

Use a dedicated data directory for separate instances. The runtime can automatically choose a non-overlapping service bundle when another local WildRoot instance already occupies the default ports.

wildrootd

cargo run -p wildrootd -- --config config/mainnet.toml

Desktop

The GUI is a complete node process.

The desktop app uses direct shared state and in-process notifications for live wallet, node and explorer updates instead of polling its own localhost HTTP services. Timed refresh remains only a reconciliation fallback.

Automatic first-run port fallback plus UPnP/NAT-PMP support can assist node connectivity. Services such as Stratum remain loopback by default unless the operator intentionally exposes them.

wildroot-gui

cargo run -p wildroot-gui -- --config config/mainnet.toml

Storage & recovery

Crash consistency stays conservative on checkpoint acceptance.

Per-checkpoint durability

Accepted checkpoints are made crash-consistently durable before the next checkpoint is accepted. Experimental whole-page durability batching was rejected after real live-node testing.

Incremental clean sync

When the application scan is current and the open DAG is empty, clean direct-tip catch-up updates coinbase/application state incrementally rather than replaying unchanged history from genesis.

Full deterministic recovery

Forks, reorgs, non-empty frontiers, open-DAG state and recovery paths retain full deterministic reconstruction rather than relying on the direct-tip fast path.