v1.1.11 — Mac perf fix + miner self-heal on rejected shares

⚠️ Linux users: the AppImage in this release has a display bug — sending shows "RME" instead of "GLAC". Funds are sent correctly as GLAC on chain, only the wallet UI label is wrong. Use v1.1.14 instead.

Quick follow-up to v1.1.10. Mac users should upgrade for the perf fix; other platforms are version-bump-only.

What changed

Mac (the perf fix)

The v1.1.10 self-heal logic added per-share g_lock acquisitions in the async submitter. That same lock is acquired by every dispatch_apply worker thread on best-bits + winner updates, creating new contention across 8 cores. Result: noticeably slower hashing after the v1.1.10 build. v1.1.11 switches the counters to <stdatomic.h> — no lock, no contention, hashrate back to v1.1.9 speed.

All four miners

Defensive self-heal on consecutive invalid-share rejections. After 3 in a row, the miner drops its cached epoch dataset, refetches the job, and rebuilds against the fresh seed_hash. Recovers from missed epoch transitions in seconds — before the pool's ban kicks in. (Mac/Windows/Linux/Android all carry this; the perf fix above is Mac-only.)

Pool (already live)

• Invalid-share ban threshold raised 10 → 25
• Early-warning log at 10 invalid shares
• Successful share resets per-wallet bad-count
• Every invalid rejection now logs the full diagnostic (seed prefix, nonce, computed hash, top-64 bits, share difficulty)
• New pool_verify_share_v2 returns the failing hash so the Python side can log it

Downloads

• Mac (universal, 14+) — Glaciem-Miner-macOS.zip
• Windows (x86_64, AVX2) — Glaciem-Miner-Windows.exe
• Linux (x86_64) — Glaciem-Miner-Linux.AppImage ⚠️ has RME display bug, use v1.1.14
• Android (arm64, API 26+) — Glaciem-Miner-Android.apk

Mac users on v1.1.10 should upgrade for the perf fix. Other platforms can stay on v1.1.10 — the version bump is for catalog consistency, no functional change.