proof of work failed error | Bitcointalksearch.org

pereira4

legendary

Activity: 1610

Merit: 1183

Quote from: callmejoe on June 07, 2019, 05:04:07 PM

just strange to me that i never see those proof of work failed errors on the x86 machine. but very often on the raspberry pi.

it is what it is i guess.

thanks

You could use bitpeers and extract the data from peers.dat. What this program does is dump data from the file in human readable format. What you want to do is get the IP's from your x86 and load them within the raspberry pi node, then monitor the log and see if you are getting the same volume of invalid proof of work errors.

Simply do this:

Code:

bitpeers --filepath /mnt/doge/.dogecoin/peers.dat --addressonly

then open the generated .json file with a text editor and you will have all the IP's which you can use on the raspberry.

callmejoe

jr. member

Activity: 45

Merit: 22

just strange to me that i never see those proof of work failed errors on the x86 machine. but very often on the raspberry pi.

it is what it is i guess.

thanks

khaled0111

legendary

Activity: 2702

Merit: 3045

Top Crypto Casino

Quote from: callmejoe on June 07, 2019, 11:38:06 AM

i would think the 2 nodes are receiving the same information from the newtork.

A node selects random nodes to connect to, unless you add them manually. Hence, Don't expect your two nodes to receive the same data.

Obviously, the Raspberry Pi node is receiving invalid blocks from a malicious node. If it keeps broadcasting invalid blocks, your node will disconnect from it.

callmejoe

jr. member

Activity: 45

Merit: 22

i've noticed i get a lot of errors in my debug.log from my raspberry pi that i dont get from my x86 machine. i would think the 2 nodes are receiving the same information from the newtork. here is an example.

raspberry pi debug.log

Code:

2019-06-07T07:43:04Z ERROR: AcceptBlockHeader: Consensus::CheckBlockHeader: 000000fc8edcaed1073cb52440514a4c5fdec31ec4244a29a8b215467eac6345, high-hash, proof of work failed (code 16)
2019-06-07T07:43:08Z UpdateTip: new best=00000000000000000004a719e7ac40c9018f6f77ad3a65f762c244df5944e8fc height=579641 version=0x20000000 log2_work=90.715349 tx=421846274 date='2019-06-07T07:42:37Z' progress=1.000000 cache=23.5MiB(154405txo) warning='37 of last 100 blocks have unexpected version'
2019-06-07T07:44:20Z ERROR: AcceptBlockHeader: Consensus::CheckBlockHeader: 000000fc8edcaed1073cb52440514a4c5fdec31ec4244a29a8b215467eac6345, high-hash, proof of work failed (code 16)
2019-06-07T07:44:39Z ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 000000000000000000639be19a0123a1c99d9fef89f0b8ac055a77f4ef86ae3b, bad-diffbits, incorrect proof of work (code 16)

i looked through the debug.log from my x86 machine around these timestamps and there are no errors at all like this in the entire log.

raspberry pi is in listening mode and x86 is not if that makes a difference.

Topic: proof of work failed error (Read 288 times)