-
Notifications
You must be signed in to change notification settings - Fork 282
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
specify permanently hard-coded seed node locations #857
specify permanently hard-coded seed node locations #857
Conversation
I don't think adding locations guessed based on IP is a good idea, they are not reliable. |
Indeed, those guessed locations may appear to be wrong. What do you think about specifying the locations in general? We could double check with authors or search in Github history/chats. |
I suppose at least countries are reliable in this case. Also I believe https://ipinfo.io/ is reliable enough. It's what I used as a source. Seems like https://shakenodes uses some unreliable source:
|
The location added in the comments are not reliable, not verifiable, and IMO they add no value. |
Thanks for the feedback.
Can you confirm this entry is incorrect?
If it's incorrect I'll forward this to https://ipinfo.io. On their main page they state "Powering organizations around the world with reliable IP data".
If you can reply to the question above doesn't this mean the location is verifiable?
May be true if others says so as well (preferably providing at least some reasoning). My idea is to explicitly show how well different regions are represented. This is also covered in the grant proposal. |
I don't think so. Verifiable would mean that everyone can verify that the server is indeed in that location. Falci (or anyone) claiming anything isn't verification.
More of a personal opinion: this kind of data is better visualized on a map with different stats on a separate website (like hnsnodes, etc.) |
By this definition the current comments aren't verifiable as well I suppose.
Definitely, it's not a substitution of a better visualised map like hnsnodes or https://bitnodes.io. |
Physical location cannot be verified, but ownership can be by signing a message since there's a brontide key [1]. [1] https://gist.github.com/pinheadmz/680809e633467c56a3b3de33855bee38 |
I agree that locations don't give any useful information, also if you are interested you can easily look them up using service you want. maintainers of the nodes is useful information for pinging them when they go down. Otherwise it would not be part of the "set", but instead listed below where tool collected nodes are. There's no big difference between those two sets other than that. |
Could be confirmed with https://ipinfo.io, https://hnsnodes.htools.work/api/v1/snapshots/latest/reachable or https://shakenodes.
I decided to look into the permanent seed node locations during my work on opensystm/handshake-micro-grants#5. 8 are in US and 2 are in DE.