2018-11-06 17:21:11 received: headers (164003 bytes) peer=331
2018-11-06 17:21:11 headers[0].hashPrevBlock: d0842ddc706cae4bc48ae461d0d6a5f5a2e1a7ad2e59b559104a21ac23f9867a npindexBestHeader->nHeight: 418534
2018-11-06 17:21:11 Received non full headers. bnPrimeChainMultiplier == 0. Possibly an old client.
2018-11-06 17:21:11 more getheaders (404138) to end to peer=331 (startheight:409148)
2018-11-06 17:21:11 sending getheaders (997 bytes) peer=331
2018-11-06 17:21:11 fCanDirectFetch=1 pindexLast->IsValid(BLOCK_VALID_TREE)=1 chainActive.Tip()->nChainWork=0000000000000000000000000000000000000000000000000001beed3beaccff pindexLast->nChainWork=0000000000000000000000000000000000000000000000000001beed3b5a87ce
2018-11-06 17:21:11 received: getdata (18003 bytes) peer=331
2018-11-06 17:21:11 received getdata (500 invsz) peer=331
2018-11-06 17:21:11 received getdata for: block 1dd0bf3866d04aca245a430cf6a1492df99ad873405bd4a62ff18ccc1ed00112 peer=331
I get this on my testnet dubug.
I using DatacoinCore.Veter:0.15.99.8
Hi benxy031,
Thanks for replying. Timestamps seem to indicate my 8.6.0 node received 1dd0bf3866d04aca245a430cf6a1492df99ad873405bd4a62ff18ccc1ed00112 from you and the other Veter nodes and then banned them.
This is concerning and may be alarming if somebody else with the earlier wallet cannot disprove there may be anything wrong.
At the moment though, it would seem there is disagreement in the ComputeMinWork() aspect of protocol between the original code and the Veter wallet.
We're going to have to see what the other node operators are able to report and then evaluate some options to assess the situation.
Best Regards,
-Chicago