I like the idea but something isn't quite right. The pool runs but when trying to connect to it an error is thrown by the mining client (CPUMiner in this case):
[2026-06-09 08:20:47] JSON decode failed(1): '[' or '{' expected near '<'
[2026-06-09 08:20:47] JSON decode failed(1): '[' or '{' expected near '<'
Or the error as seen from PBPool:
127.0.0.1 - - [09/Jun/2026 08:20:07] code 400, message Bad request version ('["cpuminer-opt-26.1-x64W"]}')
127.0.0.1 - - [09/Jun/2026 08:20:07] "{"id": 1, "method": "mining.subscribe", "params": ["cpuminer-opt-26.1-x64W"]}" 400 -
192.168.4.45 - - [09/Jun/2026 08:20:24] code 400, message Bad request version ('["cpuminer-opt-26.1-x64W"]}')
192.168.4.45 - - [09/Jun/2026 08:20:24] "{"id": 1, "method": "mining.subscribe", "params": ["cpuminer-opt-26.1-x64W"]}" 400 -
192.168.4.45 - - [09/Jun/2026 08:20:47] code 400, message Bad request version ('["cpuminer-opt-26.1-x64W"]}')
192.168.4.45 - - [09/Jun/2026 08:20:47] "{"id": 1, "method": "mining.subscribe", "params": ["cpuminer-opt-26.1-x64W"]}" 400 -
Is this due to something specific to CPUMiner or is this a bug in the pool's interpretation of the miner's signature?
I like the idea but something isn't quite right. The pool runs but when trying to connect to it an error is thrown by the mining client (CPUMiner in this case):
[2026-06-09 08:20:47] JSON decode failed(1): '[' or '{' expected near '<'
[2026-06-09 08:20:47] JSON decode failed(1): '[' or '{' expected near '<'
Or the error as seen from PBPool:
127.0.0.1 - - [09/Jun/2026 08:20:07] code 400, message Bad request version ('["cpuminer-opt-26.1-x64W"]}')
127.0.0.1 - - [09/Jun/2026 08:20:07] "{"id": 1, "method": "mining.subscribe", "params": ["cpuminer-opt-26.1-x64W"]}" 400 -
192.168.4.45 - - [09/Jun/2026 08:20:24] code 400, message Bad request version ('["cpuminer-opt-26.1-x64W"]}')
192.168.4.45 - - [09/Jun/2026 08:20:24] "{"id": 1, "method": "mining.subscribe", "params": ["cpuminer-opt-26.1-x64W"]}" 400 -
192.168.4.45 - - [09/Jun/2026 08:20:47] code 400, message Bad request version ('["cpuminer-opt-26.1-x64W"]}')
192.168.4.45 - - [09/Jun/2026 08:20:47] "{"id": 1, "method": "mining.subscribe", "params": ["cpuminer-opt-26.1-x64W"]}" 400 -
Is this due to something specific to CPUMiner or is this a bug in the pool's interpretation of the miner's signature?