v0.9.10 — clearer startup, and the resident-tree flag
Two fixes aimed at first-run confusion:
-
"Workers stalled or crashed" during a normal first run is fixed. While the model is
downloading (a one-time, possibly many-minute IPFS fetch) or the possession index is
building, the miner produces 0 h/s — that is expected, not a crash. It used to print
Workers stalled or crashed…every 10 s regardless. It now says what is actually
happening:still downloading the model…,preparing models…, orbuilding the possession index / resident tree… — mining starts automatically when done, this is NOT a stall. A genuine 0 h/s when not preparing still warns as before. -
Resident Merkle tree is a proper CLI flag, guaranteed OFF by default.
--resident-tree
turns it on (needs a lot of RAM — ~9.6 GB at tier 0; only useful for SOLO mining);
--no-resident-treeforces it off and overrides a strayKERYX_RESIDENT_TREE=1env
var left in a flight sheet. The miner logs the state at startup (PoM resident tree: on/ON).
If you have an 8 GB rig: do nothing, it is already off.
Carries all of v0.9.7-0.9.9: per-GPU efficiency stats + HiveOS hashrate-unit fix, the
keryxd>=1.4.4 solo claim gate, per-GPU fault recovery, and batched escrow claims.
Linux NVIDIA assets attached (modern/legacy/pascal x HiveOS/SMOS/mmpOS/linux + SHA256SUMS).
Windows/macOS via CI; AMD from the AMD line.