7
I have my Core 0.13.1 node configured to connect to 16 nodes, and invariably I see it connected only to other 0.13.1 nodes, even though, according to bitnodes leaderboard, these nodes form a minority.
Why is the selection logic this restrictive?
I am also noticing my 0.13.1 node that accepts incoming connecting as relatively overloaded I/O-wise since it upgraded.
I can understand this selection logic being necessary once SegWit activates, but why already, given we don't know yet whether SegWit will activate?
I think I've had a few other nodes connected to mine yesterday, but I've also had the impression that it takes much longer to get incoming connections and when my node starts up, it almost immediately only has 0.13.1 and 0.13.99 nodes connected to it. – So, it seems likely that there is a strong preferential connecting, but not an exclusive connecting to 0.13.X clients. – Murch – 2016-11-04T13:19:39.353