-
Notifications
You must be signed in to change notification settings - Fork 54
Mainnet seeds are not working #2241
Copy link
Copy link
Closed
Labels
bugSomething isn't workingSomething isn't workingeffort: SSmall effort — a few hours or lessSmall effort — a few hours or lesspriority: highHigh priority — address soonHigh priority — address soonstaleLikely outdated — candidate for closingLikely outdated — candidate for closing
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingeffort: SSmall effort — a few hours or lessSmall effort — a few hours or lesspriority: highHigh priority — address soonHigh priority — address soonstaleLikely outdated — candidate for closingLikely outdated — candidate for closing
Type
Projects
Status
Done
Expected Behavior
Users should be able to connect to thenetwork using latest SDK as provided by documentation
Current Behavior
Mainnet seeds are not working. When you install SDK from the npm, it fails to sync and fails silently for the user, because there are no error handlers implemented, it just keeps syncing forever.
If you raise the log level via envrionment, you can see a message:
Telnet is also not possible on the seed address.
This is very important because it highly affecting people's performance and confusing them. Its not easy to insert an IP manually too, because you need to know where to grab it beforehand.
Possible Solution
Steps to Reproduce (for bugs)
Context
Your Environment