SubGeniusFinance/Offerings-to-Cthulhu
Watch
1
0
Fork
You've already forked Offerings-to-Cthulhu
 0
Code Issues 4 Pull requests Projects Releases 3 Packages Wiki Activity
3 releases 44 tags
  • wallet-miningtab-stratumfix-20260909 6917dbf839

    Mining tab: share-multiplier + reconnect fixes (BLOATED SQUID successor) Pre-release

    btcbob released this 2026-09-09 00:14:32 +00:00 | 13 commits to main since this release

    Windows x64 wallet with the in-wallet Mining tab. Successor to Offerings-miningtab-private-20260812-133421-win64.zip, the BLOATED SQUID build linked from 23skidoo.info/downloads.

    The first (OFF) binary built entirely on our own hardware — dependencies, configure, compile and link all on vps3, published from our own Forgejo. No GitHub Actions anywhere in the chain.

    Pool mining was paying you 256x too little

    The pool client screened its own candidate shares against a bar 256x stricter than the pool's, because it omitted the coin template's shareMultiplier. It did not fail loudly — shares landed, nothing looked wrong — it simply submitted roughly one share for every 256 it should have, and was paid accordingly. A source comment asserted the multiplier was 1; for (OFF)/quark it is 256.

    The value was measured, not copied from the sibling (BOB) fix, because the reference miner disagrees for this algorithm: cpuminer-multi has no ALGO_QUARK case in its target switch and falls through to factor 1. Against the live pool on 2026-09-08, with a proxy dividing the announced difficulty by 256, the unpatched client produced 246 accepted shares and 0 rejected in 30 seconds — where the shipped build manages about one. Had the pool's multiplier been 1, that same proxy would have made the client 256x too loose and the pool would have rejected nearly all of them.

    Three reconnect fixes

    • Rejected shares were counted nowhere: the error branch returned before the accounting block, so the UI read accepted 0 / rejected 0 regardless — and one rejected share overwrote the connection-status string, making the wallet report the pool as down.
    • Reconnect did not clear the previous session's extranonce, difficulty or job, so workers resumed dead work the instant authorize succeeded.
    • The reconnect backoff ladder never reset, because it tested a flag its own error path had already cleared.

    The ladder is gated on having authorized, not merely connected: miningcore closes a banned IP inside AcceptConnection, after the TCP handshake, so re-arming on connect would turn a mistyped payout address into a permanent 5-second reconnect loop.

    Also in here

    The Overview "The Deep" chain-vitals panel (9a037588, 4702d957), same as the previous mining build.

    Provenance

    Built from 6917dbf8 on branch fix/stratum-share-multiplier, a clean checkout of fb5378ac — the exact commit the published BLOATED SQUID came from — plus the fixes above. Base source blob verified identical to the published build before patching.

    Note this branch is behind (OFF) main by roughly a dozen commits, including the widened fixed seeds (66ee4904) and the v2.1.3 version bump. Those are deliberately not included: this is a targeted bugfix on the published build, not a rebase.

    sha256 a2462ab3bc824dae227a1d07a217ea7752468012738fb6cc8b2a0b1237171367

    Downloads