Keryx-node-v1.2.5-OPoI

Keryx v1.2.5 — Difficulty Re-Anchor Recovery

MANDATORY UPGRADE — before DAA 22035000

Every node — including solo miners' and pools' nodes — must be running v1.2.5 before the chain reaches DAA 22035000. Any node still on v1.2.4 will diverge (fork) at that point.

---

The bug being fixed

Since the v1.2.4 relaunch, difficulty stayed stuck at its floor (genesis). At that level the PoW is trivial: the network produces a flood of blocks, the DAG blows up, and the nodes' (single-threaded) virtual resolution can no longer keep up.

Visible symptoms:

• the validated chain advanced at only ~0.3 blocks/s (far below the 10 BPS target);
• miners saw their hashrate collapse (e.g. ~6 MH/s on an RTX 3090) — the GPU was actually idle waiting for templates, not slowed down;
• the difficulty auto-adjustment could not recover on its own (validated production < target → difficulty stays at the floor → the flood continues).

Confirmed by profiling: the bottleneck was the nodes' virtual resolution choked by an abnormal DAG — not the miner, not the algorithm, not OPoI.

The fix

v1.2.5 introduces a difficulty re-anchor gated at a future DAA:

• at DAA 22035000, the difficulty window restarts from a sane value (0x1d080000, calibrated for ~10 BPS) instead of the floor;
• the standard auto-adjustment then takes over and converges to the network's real hashrate within ~1–2h.

The spiral is broken cleanly, at a known height announced in advance.

Action required

1. Update keryxd to v1.2.5 (build / provided binary).
2. Restart your node before DAA 22035000.
3. That's it — the mining binary does not change, this only affects the node.

Compatibility & safety

• Before the gate, v1.2.5 behaves identically to current nodes → you can upgrade right now with no fork risk.
• Divergence happens only at DAA 22035000, and only for nodes still on v1.2.4.