You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
The discovery should start with the seed peers but when the interval executes again, it should use some of the newly discovered peers as the new seeds.
Actual behavior
There is a bug in the current discovery algorithm which means that our node always go back to the seed peers for discovery.
Steps to reproduce
Check the code.
Which version(s) does this affect? (Environment, OS, etc...)
0.1.0-alpha.9
The text was updated successfully, but these errors were encountered:
Expected behavior
The discovery should start with the seed peers but when the interval executes again, it should use some of the newly discovered peers as the new seeds.
Actual behavior
There is a bug in the current discovery algorithm which means that our node always go back to the seed peers for discovery.
Steps to reproduce
Check the code.
Which version(s) does this affect? (Environment, OS, etc...)
0.1.0-alpha.9
The text was updated successfully, but these errors were encountered: