Confirmed — same bug, lost block 947633 to it last week

Hi @aaron3481, your warning saved me from losing more. I lost 3.126 BCH on April 20, 2026 (block 947633) to this exact issue — coinbase reward sent to spurious hash160 aef1328e1a44e182b07f812faf87269e3a50e0a2, non-recoverable. After your block 927030 hint I dug into the code and found the root cause.

Root cause: in libckpool.c::address_to_txn() and bitcoin.c::validate_address(), bare CashAddr (no explicit bitcoincash: prefix) falls through to the Base58 decoder, producing spurious hash160 bytes that go into the coinbase scriptPubKey.

Fix: I've opened PR #4 with a 28-line patch that auto-prefixes bare CashAddr starting with q/p/Q/P. Validated in production on solofury.com since April 23 — 27+ billion shares accepted, 0.10% reject rate, no regression.

For now, until the fix is merged: anyone running this pool software for production solo mining should switch to legacy 1... addresses immediately, OR cherry-pick the patch from PR #4. The bug is silent — pool logs show "Authorised" and shares accepting normally. You only find out when you find a block and the funds are gone.

Sorry it took 5 months for someone to confirm this @aaron3481. Hopefully this saves the next pool operator from a hard lesson.

DO NOT USE bitcoincase address as your pool address!! #2

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions