Stay connected, don't go to shady solo pools, here you can verify the jobs I send, it's fair enough better
I tried to verify the payout amounts and addresses that you configured on your pool. I am using cgminer in its latest version. Unfortunately it failed completely with your pool. With eg. cgminer you can easily check what happens in case of a block found by querying the pool and see the coinbase transaction it returns.
Here's an example with solo.ckpool.org with a correct and expected output:
Pool stratum+tcp://solo.ckpool.org:3333:
{
"result": {
"txid": "497ee53104c2840e3ac3bd41d534711a243537de8d7ee6bbe853f4dcc1390cb8",
"hash": "497ee53104c2840e3ac3bd41d534711a243537de8d7ee6bbe853f4dcc1390cb8",
"version": 1,
"size": 219,
"vsize": 219,
"weight": 876,
"locktime": 0,
"vin": [
{
"coinbase": "03c29a0b0004995d5a6304a598bc0e0c890a198600000000000000000a636b706f6f6c112f736f6c6f2e636b706f6f6c2e6f72672f",
"sequence": 4294967295
}
],
"vout": [
{
"value": 6.1784937700000002,
"n": 0,
"scriptPubKey": {
"asm": "OP_DUP OP_HASH160 06040de94c96094d379a25427510d4c3d83fd7aa OP_EQUALVERIFY OP_CHECKSIG",
"desc": "addr(1YourPayoutAddressxxxxxxxxxteJhsz)#3wcn68cg",
"hex": "76a91406040de94c96094d379a25427510d4c3d83fd7aa88ac",
"address": "1YourPayoutAddressxxxxxxxxxteJhsz",
"type": "pubkeyhash"
}
},
{
"value": 0.1260917,
"n": 1,
"scriptPubKey": {
"asm": "OP_DUP OP_HASH160 f4cbe6c6bb3a8535c963169c22963d3a20e76869 OP_EQUALVERIFY OP_CHECKSIG",
"desc": "addr(1PKN98VN2z5gwSGZvGKS2bj8aADZBkyhkZ)#5rs4qewl",
"hex": "76a914f4cbe6c6bb3a8535c963169c22963d3a20e7686988ac",
"address": "1PKN98VN2z5gwSGZvGKS2bj8aADZBkyhkZ",
"type": "pubkeyhash"
}
},
{
"value": 0.0,
"n": 2,
"scriptPubKey": {
"asm": "OP_RETURN aa21a9ed8d6dcf633056c61acab3dded8cd2e93b5547fbb23e3d9cf8b40bfcafe8364c92",
"desc": "raw(6a24aa21a9ed8d6dcf633056c61acab3dded8cd2e93b5547fbb23e3d9cf8b40bfcafe8364c92)#ks50402f",
"hex": "6a24aa21a9ed8d6dcf633056c61acab3dded8cd2e93b5547fbb23e3d9cf8b40bfcafe8364c92",
"type": "nulldata"
}
}
]
},
"error": null,
"id": 0
}
as we see, 2% fee (here 0.1260917
BTC) goes to
1PKN98VN2z5gwSGZvGKS2bj8aADZBkyhkZ (owned by the pool operator) just as promised and promoted on
his pool site. The reward of 6.1784937700000002
BTC in that example would go to users payout address.
Unfortunately and as not expected, the
query does not work at all on your pool as it fails in the beginning with the error:
Failed json_rpc_call
For me it looks like that your pool spits out some json incompatible data, with which the mining software cgminer or the bitcoin core linked to it cannot process. Just guessing though. However, the query works against
all other known pools available out there without issues, just your pool returns nothing but that error. I personally would avoid your pool under these circumstances, because it means for me: if my miner would find a block then I can't trust that I would get paid. Not to mention that the miner would have problems with the call at all because he can't seem to communicate properly.
Can you provide more info on why well-known and widely used mining software such as the latest version of cgminer used here spits out a false check?
Strange. Have you tried my method ?
I tested the pool with CPUMINER, Antminer, Whatsminer, but not CGMiner.