Hi,
The question is in the title : is there any (implemented) heuristic to priorize registered DHT node in routing table buckets ?
I have seen that :
- By design, buckets keep long living DHT peers
- There is only 1 single IP address occurence stored
But, I have seen nothing about :
- Bonus/Malus according to peer’s activity (add/get/pin action)
- Bonus/Malus according to rarity of provided blocks
- Bonus/Malus according to its own bucket content
Are they implementable or should it breaks any IPFS/DHT intrinsic logic ?