Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maintain buckets according to specs #45

Open
herr-seppia opened this issue Oct 25, 2021 · 0 comments
Open

Maintain buckets according to specs #45

herr-seppia opened this issue Oct 25, 2021 · 0 comments
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)

Comments

@herr-seppia
Copy link
Member

Describe what you want implemented
The bucket periodic maintenance need to follow the specs
According to white paper:

  • Each node periodically refreshes every bucket it has not seen some activity from in the last hour: for each such bucket, it picks a random ID with appropriate distance and performs a look up to populate its buckets with fresh routing information.
  • The lookup procedure allows a node to retrieve a set of k nodes closest to a specific ID in the address space.
  • The procedure of finding the k closest nodes is carried out by iteratively narrowing down the search space and issuing FIND_NODE messages to nodes which are closer to the ID.

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

@herr-seppia herr-seppia added team:WebTech End to End UX / UI and blockchain type:enhancement Issues concerning code or feature improvement (performance, refactoring, etc) labels Oct 25, 2021
@autholykos autholykos added the status:minor Low priority improvements label Jan 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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)
Projects
None yet
Development

No branches or pull requests

2 participants