Carsen ...
For some strange reason since we have moved to the later versions of the daemon on our pool, almost EVERY block has been an orphan. Not so with the previous daemons, just the latest ones.
Is there a change in ports or settings we have missed in the .conf or elsewhere?
I initially thought it was a one off thing, but this is SO consistent that it is more than just coincidence. Trying to locate the issue seems to be a dead loss for us, and cannot seem to locate what may have gone astray. Is there a list of ports/configs/settings that we need to have with these newer daemons?
Thanks,
#crysx
Maybe just more orphans now with more people staking, a lot more people staking now.
Ports are all the same as usual, RPC port is 32339
Main change for mining pools was within the getblocktemplate rpc command for pools, it now has masternode payment flags and 33% of the reward of the block will be given to a masternode.
Here is what it returns now, will show true soon with payments going live:
{
"version" : 6,
"previousblockhash" : "000000000004e74d092eb4c9f8671897858d2104e0a001071e8beb406928684e",
"transactions" : [
],
"coinbaseaux" : {
"flags" : ""
},
"coinbasevalue" : 300000000,
"target" : "00000000000da0ff000000000000000000000000000000000000000000000000",
"mintime" : 1521359242,
"mutable" : [
"time",
"transactions",
"prevblock"
],
"noncerange" : "00000000ffffffff",
"sigoplimit" : 20000,
"sizelimit" : 1000000,
"curtime" : 1521359462,
"bits" : "1b0da0ff",
"height" : 644916,
"payee" : "",
"payee_amount" : "",
"masternode_payments" : false,
"enforce_masternode_payments" : false
}
