We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
we need to figure out how to layout our storage for peer information in order to keep track of things like which peers are connected, their accepted protocols/address etc. We can draw on inspiration from libp2p: https://github.com/libp2p/js-libp2p/tree/0.28.x/src/peer-store and hyperswarm: https://github.com/hyperswarm/hyperswarm For now I think something simple and extensible is appropriate.
The text was updated successfully, but these errors were encountered:
A custom peer store and peer info was implemented in PR #40.
Sorry, something went wrong.
robert-cronin
No branches or pull requests
we need to figure out how to layout our storage for peer information in order to keep track of things like which peers are connected, their accepted protocols/address etc. We can draw on inspiration from libp2p: https://github.com/libp2p/js-libp2p/tree/0.28.x/src/peer-store and hyperswarm: https://github.com/hyperswarm/hyperswarm
For now I think something simple and extensible is appropriate.
The text was updated successfully, but these errors were encountered: