Closed Retropex closed 3 months ago
I'm not exactly sure how this code path was achieved but the underlying issue has been fixed by initializing hashrate to 0. https://github.com/benjamin-wilson/public-pool/commit/de2b41a3c1a98a328ef056bdfd1f7d7c6abb57c0
Still getting it:
It also seems to not only be duplicate share bug but also discard valid share since the best difficulty miss match on the pool UI and bitaxe UI.
Does this only happen on testnet4?
yes, it seems to work normally on mainnet:
Ah ok, I haven't tested it with testnet4 and is likely the problem. I'm going to close these issues and make a single one for that.
getting duplicate share on testnet4 with a bitaxe ultra