I'm not really an expert on the blockchain details either, but for the attempting to generate 19909 BBP on the stale block part, that'd probably be because the node you're running on your machine accepted the block that it mined itself until the blockchain rejected it. Something like:
-you mined a block
-your node said it was valid and adds it to your local copy of the blockchain
-your wallet reads the block and adds 19909 BBP to your immature balance
-a fraction of a second later you receive a a block of the same height from the p2p network
-your node checks it and because its solution is a higher difficulty than the block you mined your node orphans the block you found and replaces it with the block you received
-reading the new blockchain your wallet removes the 19909 immature BBP from your wallet.
The order of the errors within the same timeframe in the debug log probably don't mean much since it's heavily multithreaded. That should be a rare event, but because of the occasionally difficulty drops we're seeing with Biblepay it's probably more common than it should be. But, it's something that would affect everyone equally, so it shouldn't influence the payout statistics over time.
Thank you for your effort to break it down, everything is clear as day. I don't think this is an issue as long as it happens rarely. One more user here mentioned he had the same situation, the wallet briefly showed him the new credit and then disappeared, but I still think that's sufficiently rare, as I found only one stale block in 7 debug logs across 7 machines mining for 3 days.-you mined a block
-your node said it was valid and adds it to your local copy of the blockchain
-your wallet reads the block and adds 19909 BBP to your immature balance
-a fraction of a second later you receive a a block of the same height from the p2p network
-your node checks it and because its solution is a higher difficulty than the block you mined your node orphans the block you found and replaces it with the block you received
-reading the new blockchain your wallet removes the 19909 immature BBP from your wallet.
The order of the errors within the same timeframe in the debug log probably don't mean much since it's heavily multithreaded. That should be a rare event, but because of the occasionally difficulty drops we're seeing with Biblepay it's probably more common than it should be. But, it's something that would affect everyone equally, so it shouldn't influence the payout statistics over time.
The 3rd error log I don't really know, maybe the dev has an idea. I noticed it's block 2770, which is a multiple of 10 so it'd be a tithe block so it might be related to that. Or maybe it was a block that you received from the network that your node rejected. 0000001ae8594b890ff5b97168ba3f57ec1cf64e2c3351275e592ed6a7a52396 is the hash for block 2770 though, so the network didn't seem to reject it.
Smart guess about the tithe block, but that occurrence was accidentally a multiple of 10. Here, I'll paste another one, the newest.I'd try to audit the code myself, but C++ goes over my head for the most part. I should really get around to learning the basics one of these days...
Good idea, same here, but I'll try to skim through the code anyway.Edit:
One very important thing to note is that the invalid block error on some block (for example block 2782 in the above paste) only appears on that machine. On all 6 others it's normal, like this:
Quote
2017-08-12 08:39:49 UpdateTip: new best=00000024a3327afa5e3ff620607e48841ec35c6a92a554a132e0dbb616b5526d height=2782 log2_work=32.427115 tx=3308 date=2017-08-12 08:39:47 progress=0.999999 cache=0.0MiB(233tx)
2017-08-12 08:39:49 ProcessNewBlock : ACCEPTED
2017-08-12 08:39:55 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we are, done
2017-08-12 08:59:27 UpdateTip: new best=000000018734cbb6422e82aeaa2f52162760f95ea4d485a2a5c8de3a46bc47b9 height=2783 log2_work=32.43188 tx=3309 date=2017-08-12 08:59:25 progress=0.999999 cache=0.0MiB(234tx)
2017-08-12 08:59:27 ProcessNewBlock : ACCEPTED
2017-08-12 08:59:33 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we are, done
2017-08-12 08:39:49 ProcessNewBlock : ACCEPTED
2017-08-12 08:39:55 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we are, done
2017-08-12 08:59:27 UpdateTip: new best=000000018734cbb6422e82aeaa2f52162760f95ea4d485a2a5c8de3a46bc47b9 height=2783 log2_work=32.43188 tx=3309 date=2017-08-12 08:59:25 progress=0.999999 cache=0.0MiB(234tx)
2017-08-12 08:59:27 ProcessNewBlock : ACCEPTED
2017-08-12 08:59:33 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we are, done
Then some other block will be invalid again only on one machine (6 of them are identical btw), so that leads me to believe those are found blocks which are invalid for some reason.
. Do you know if your friend is using the windows wallet?