Maintain buckets according to specs #45
Labels
status:minor
Low priority improvements
team:WebTech
End to End UX / UI and blockchain
type:enhancement
Issues concerning code or feature improvement (performance, refactoring, etc)
Describe what you want implemented
The bucket periodic maintenance need to follow the specs
According to white paper:
ID
with appropriate distance and performs a look up to populate its buckets with fresh routing information.k
nodes closest to a specificID
in the address space.k
closest nodes is carried out by iteratively narrowing down the search space and issuingFIND_NODE
messages to nodes which are closer to theID
.Describe "Why" this is needed
Actually the nodes lookup maintenance is performed against a random known peer's ID inside the bucket instead of a random ID
Describe alternatives you've considered
Keep going with the actual implementation
Additional context
To handle properly this issue, the issue #44 should be resolved first
The text was updated successfully, but these errors were encountered: