0
What countermeasures does Bitcoin currently have in place to limit Sybil attacks (ie of full nodes [not miners]) and eclipse attacks?
In particular, it seems like an important countermeasure would be to attempt to give your connections only about as much resources (bandwidth/processing/etc) as they're giving back to you, so as to ensure that a sybil attacker must cost approximately the same amount as an honest node. But I get the feeling this doesn't exist. Does it?
Are there other countermeasures in place currently?
I understand PoW, but that's not the type of Sybil attack I'm talking about. The Sybil attack I'm talking about is about an entity creating many bitcoin network nodes and doing nefarious things to the network, like slowing down traffic or eating up connections. The eclipse prevention mechanism you mention helps for certain things, but not for others. For example, it doesn't prevent a Sybil attacker from matching transactions to IP addresses. – B T – 2019-07-27T21:31:49.183
nodes can be run anonymously to prevent IP address matching. – JBaczuk – 2019-07-27T21:44:28.530
2Incoming connections are actually also regulated, but only once the max connections limit is reached. After that, new connections are still allowed, but subject to certain scoring conditions (including IP range based), and if the new connection is better than an existing one, the existing one is disconnected; otherwise, the new one is. – Pieter Wuille – 2019-07-27T23:38:41.477
Interesting. @PieterWuille what other scoring conditions are there? Is there a good concise list somewhere (maybe in a source file)? – B T – 2019-07-31T17:32:30.500