Skip to content

Changelog

Every fix and update to the NexusPool core, with its date.

v0.6.26.29
  • Forward-compatibility for Bitcoin's upcoming Consensus Cleanup (BIP54): the pool now builds its coinbase transaction to meet the new coinbase requirement ahead of activation, so every block the pool finds stays valid once the soft fork takes effect. It remains fully valid under today's rules; no effect on mining, share accounting, or how a won block is paid out.
v0.6.26.28
  • Foundation for remote rig insight (ANI): the pool can now securely accept a rig's own efficiency and delivery-health readings even when it can't reach the rig directly, authenticated by the fact that the rig is actively mining from your address. No shared secret, and a reading from any other source is rejected. This brings the per-rig effective-efficiency and delivery-health view within reach of remote miners, not just same-network setups. Read-only, authenticated and rate-limited; it never affects mining, share accounting, or won blocks.
v0.6.26.27
  • Reliability: a rig whose telemetry briefly drops out is no longer left behind. The pool now holds each rig at its correct, measured-hashrate difficulty through a gap, frozen at the last known-good value until fresh readings return, instead of drifting to a coarse fallback, and slower-to-respond rigs are discovered reliably. Your personal dashboard also flags any rig whose share delivery looks off (stale readings or off-target difficulty). No effect on share accounting or won blocks.
v0.6.26.26
  • Privacy: on the public dashboard, a rig's operator-sensitive details, its LAN hostname and stealth/quiet-mode indicators (including suppressed-share counts), are no longer returned just because someone knows your (public) Bitcoin address. Hardware facts (model, chip count and health, hashrate, temperature, best difficulty) stay visible. No effect on mining, share accounting, or won blocks.
v0.6.26.25
  • Security hardening (defense-in-depth; no effect on mining, share accounting, or won blocks): the pool engine now suppresses operating-system core dumps so a process crash can never persist the pool's signing key to disk, and its one cryptographic dependency is pinned to a specific verified release for reproducible builds.
v0.6.26.24
  • Rigs now pick up their correct, measured-hashrate difficulty even while they stay connected. Before, a rig that was already online when its telemetry first arrived kept its old (too-high) difficulty until it happened to reconnect; now it settles at the right level within a few minutes on its own, no reconnect or restart needed.

Page 6 of 8 · v0.6.26.29 – v0.6.26.24

Changelog: earlier releases, page 6 of 8 · NexusPool