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

Refactoring: move peer addressed from Discovery to Peerset data store #518

Open
dmitry-markin opened this issue Mar 3, 2023 · 0 comments
Labels
I4-refactor Code needs refactoring.

Comments

@dmitry-markin
Copy link
Contributor

dmitry-markin commented Mar 3, 2023

This is a part of Notifications refactoring outlined in #556 and the next logical step after splitting Peerset into data store & connection establishment components paritytech/substrate#13531.

The goal is to move known addresses from Discovery behavior to the new Peerset data store, where it should be easily accessible by all the protocols. This will also facilitate serializing the peer set to disc and reloading it on startup #565.

@dmitry-markin dmitry-markin changed the title Research/refactoring: moving peer addressed from Discovery to Peerset data store Refactoring: move peer addressed from Discovery to Peerset data store Mar 3, 2023
@altonen altonen transferred this issue from paritytech/substrate Aug 24, 2023
@the-right-joyce the-right-joyce added I4-refactor Code needs refactoring. and removed I7-refactor labels Aug 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I4-refactor Code needs refactoring.
Projects
Status: Backlog 🗒
Development

No branches or pull requests

2 participants