ABC 0.14.5: lots of 'Not relaying invalid transaction' msgs from ABC 0.14.4 (during bc catch-up)

[BitCrypto]

Hi,

I've just installed Bitcoin ABC on a new node, version 0.14.5. (Bitcoin ABC Daemon version v0.14.5.0-5dba98f)

I've downloaded 10 GB of blockchain data from another node (pruned), maybe a day old, so that it doesn't need to download the entire blockchain. I've set the node to 20 GB of data before pruning.

I have whitelisted another Bitcoin ABC node on the same local network, and connected the two using addnode=IP in the bitcoin configuration file.

The behavior I am about to describe, only happens during catching-up, after the bitcoin node is at the correct block height, this behavior corrects.

The log file gives me many of the following errors:

2017-07-26 03:20:19 Not relaying invalid transaction e9172b38faaffc5bf06c5b35fd2919937e6ce43002fe3366a3b581c745462be8 from whitelisted peer=2 (non-final (code 64))
2017-07-26 03:20:19 Misbehaving: <IP-LOCAL>:41314 peer=2 (0 -> 10)
2017-07-26 03:20:19 Not relaying invalid transaction 82af067219310b940009445abc583d4bc8110fad67185eb9d9b91dc44a4782cc from whitelisted peer=2 (non-final (code 64))
2017-07-26 03:20:19 Misbehaving: <IP-LOCAL>:41314 peer=2 (10 -> 20)
2017-07-26 03:20:19 Not relaying invalid transaction 9b336e207ead7284fb03fde9833001383f7e7468c8144480a9e0f6be592b692a from whitelisted peer=2 (non-final (code 64))
2017-07-26 03:20:19 Misbehaving: <IP-LOCAL>:41314 peer=2 (20 -> 30)
2017-07-26 03:20:19 Not relaying invalid transaction 282d23c40a7d86bc5f35d90c691933f83802ee0992eaff707e33629a99aba55b from whitelisted peer=2 (non-final (code 64))
2017-07-26 03:20:19 Misbehaving: <IP-LOCAL>:41314 peer=2 (30 -> 40)
2017-07-26 03:20:19 Not relaying invalid transaction e103504f6ac68d569a3e861c0ead24722619631da0fbd166db0a0094c5c0e17d from whitelisted peer=2 (non-final (code 64))
2017-07-26 03:20:19 Misbehaving: <IP-LOCAL>:41314 peer=2 (40 -> 50)
2017-07-26 03:20:19 Not relaying invalid transaction 03e6eff056b07c423ab2540b58ff3874703622d6dc7c58535d4d6f576a62588f from whitelisted peer=2 (non-final (code 64))
2017-07-26 03:20:19 Misbehaving: <IP-LOCAL>:41314 peer=2 (50 -> 60)
2017-07-26 03:20:19 Not relaying invalid transaction 335bed7dd12436e1b749f31054726a18c4061f09fd508c207ece7e28cd9d6a15 from whitelisted peer=2 (non-final (code 64))
2017-07-26 03:20:19 Misbehaving: <IP-LOCAL>:41314 peer=2 (60 -> 70)
2017-07-26 03:20:19 Not relaying invalid transaction 4ba754e3b9e963d562302c4b8227d5d419fa0e83bb363b51e24c9caf7b7da111 from whitelisted peer=2 (non-final (code 64))
2017-07-26 03:20:19 Misbehaving: <IP-LOCAL>:41314 peer=2 (70 -> 80)
2017-07-26 03:20:19 Not relaying invalid transaction 4b74de9f2ed331da49e9b51097d22ce2a4a9ab39549b7b62d1c8ef9130d52f42 from whitelisted peer=2 (non-final (code 64))
2017-07-26 03:20:19 Misbehaving: <IP-LOCAL>:41314 peer=2 (80 -> 90)
2017-07-26 03:20:19 Not relaying invalid transaction 2c6ad2fca9af0517c297f7fd0bb08281a74de0513e597974ce183724bdfb4d89 from whitelisted peer=2 (non-final (code 64))
2017-07-26 03:20:19 Misbehaving: <IP-LOCAL>:41314 peer=2 (90 -> 100) BAN THRESHOLD EXCEEDED
2017-07-26 03:20:19 Not relaying invalid transaction c067392dfe0afd772b28f31918e32b4307f38cfed9f0cc63a522af62afad1191 from whitelisted peer=2 (non-final (code 64))
2017-07-26 03:20:19 Misbehaving: <IP-LOCAL>:41314 peer=2 (100 -> 110)

<snip>

2017-07-26 03:28:41 Misbehaving: <IP-LOCAL> peer=1 (740 -> 750)
​

I have filtered on IP-LOCAL (and retracted the actual IP address). The transactions I viewed, were valid according to blockchain.info. There were lots of other messages relating to other peers misbehaving, and getting banned.

Of course, the other local node was whitelisted. So no issue. But in the mean time, 14 remote nodes were banned with BAN THRESHOLD EXCEEDED.

Here's some info on peer 2.

{
"id": 2,
"addr": "<IP-LOCAL>:41314",
"services": "0000000000000004",
"relaytxes": true,
"lastsend": 1501042454,
"lastrecv": 1501042449,
"bytessent": 723972,
"bytesrecv": 764282,
"conntime": 1501039170,
"timeoffset": -12,
"pingtime": 0.023721,
"minping": 0.002421,
"version": 70015,
"subver": "/Bitcoin ABC:0.14.4(EB8.0)/",
"inbound": true,
"addnode": false,
"startingheight": 477600,
"banscore": 680,
"synced_headers": 477608,
"synced_blocks": -1,
"inflight": [
],
"whitelisted": true,
"bytessent_per_msg": {
"addr": 32432,
"getdata": 96231,
"inv": 356644,
"notfound": 349,
"ping": 832,
"pong": 832,
"reject": 4760,
"sendcmpct": 33,
"sendheaders": 24,
"tx": 231674,
"verack": 24,
"version": 137
},
"bytesrecv_per_msg": {
"addr": 2850,
"feefilter": 32,
"getaddr": 24,
"getdata": 29360,
"inv": 143709,
"notfound": 30651,
"ping": 832,
"pong": 832,
"sendcmpct": 33,
"sendheaders": 24,
"tx": 555774,
"verack": 24,
"version": 137
}
},​

 

[BitCrypto]

On Reddit, I read that the latest version will fix this exact issue. I'm not sure if the report above was helpful, but I am impressed all the same by the speed at which the ABC client fixed it. Thanks!

https://download.bitcoinabc.org/0.14.6/

This release includes the following features and fixes:

• Updated Debian packaging
  
  
• Updated FreeBSD build instructions
  
  
• Fixed a bug where a node would erroneously increase the ban score of its peers when it had not caught up with the chain tip
  
  
• Added various detail with peer misbehaving
  
  
• Added tooling to help maintain good style for Python code
  
  
• Added new DNS seeds (criptolayer.net)

Signed checksums for this release

Thanks to all who contributed !

Ubuntu packages are planned to follow shortly.

Please remember to upgrade your nodes! ​

 

[freetrader]

Hey @BitCrypto :

Thanks for posting the 0.14.6 infos.

Sorry I didn't get around to making a top-level post about this.

Since you made the effort to prepare the above, can I ask you to make a top-level (in ABC subforum) official announcement post titled "Bitcoin ABC 0.14.6 is out" ?

For content you can just copy your post above.

Thanks buddy.