Every fix and update to the NexusPool core, with its date. The current stable version is highlighted.
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.
v0.6.26.23
Your rigs' measured hashrate now reaches the pool over a secure relay, so the pool sets each rig's difficulty from its real speed rather than guessing: rigs settle at the right level automatically instead of running coarser than needed. Read-only telemetry; it never affects mining, share accounting, or won blocks.
v0.6.26.22
More stable per-rig difficulty: each miner's assigned difficulty is now anchored to its real, measured hashrate, so it settles at the right level and holds there instead of drifting upward over days until the rig struggles to submit shares. A hard ceiling keeps at least one share a minute for every healthy rig, and a rig that ever ends up set too high recovers on its own within minutes, no reconnect or power-cycle needed. Won blocks are never affected.
v0.6.26.21
New public Status page: live availability of the pool with uptime bars by hour, day and week, per service (pool connection, dashboard & API, and the Bitcoin network link). The history is measured forward from launch and never backfilled, so the numbers reflect only what was actually observed. Linked from the footer.