v0.8.58

Fixed

• Reported pool difficulty now always reflects the share target the pool actually grades submits against. Some pools also announce a mining.set_difficulty value. That number is not in the same units as the per-job share target and does not gate shares, but it was being written into the same field used for the pool-diff readout. The two could race, so the difficulty shown in [stats] and in the status API could briefly display a value unrelated to the target being solved. The announced value is now kept in its own diagnostic field and never overwrites pool-diff.

Added

• A prominent warning if a pool ever rejects a share as low difficulty, which is the one signal that would mean the per-job target is not that pool's share gate.

Notes

This release changes reporting only. Mining behavior, share submission, and the proof of work are unchanged. Shares are, and always have been, solved and submitted against the pool's own per-job share target, the same target the pool grades them by.