Bittorrent spec says node ids taken at random from large numeric space. What prevents bittorrent clients from intentionally using the same node id as someone they want to attack?
Is it doing chord routing? Because chord routing pushes requests for chunks to addresses whose hashes are lexicographically adjacent to the hashes of the chunks themselves.
@enkiv2 not sure, it's using Kademlia, I'm new to this though
@cwebber i think they just don't? to mitigate that i don't think it would be exploitable in any meaningful way except a potential dos