Due to pchMessageStart not changing for testnet3, testnet3 peers wind up filling the majority -- sometimes 100% -- of their outgoing peer slots with testnet1/testnet2 peers.
This leads to basic breakdowns in block and TX relaying.
testnet3 peers difficult to find among v1/v2 clutter #1627
issue jgarzik opened this issue on July 23, 2012-
jgarzik commented at 10:06 PM on July 23, 2012: contributor
-
gavinandresen commented at 11:00 PM on July 23, 2012: contributor
Suggested easy fix: if testnet and peer version is < 0.7 : disconnect from peer.
More generally, maybe if peer version < GetArg("-minpeerversion", ...) then disconnect. I could imagine deciding on main net you don't want to talk to 0.3 nodes any more...
- gmaxwell closed this on Aug 3, 2012
-
gmaxwell commented at 2:18 AM on August 3, 2012: contributor
Solved by changing the protocol fingerprint.
- MarcoFalke locked this on Sep 8, 2021
Contributors