-
Notifications
You must be signed in to change notification settings - Fork 5
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
launch a node in Singapore instead of HK (Asia) #83
Comments
I don't think this is easily doable for 3 reasons:
I don't think this change is worth the amount of effort it would require, unless you think it's very high priority. And honestly, Waku protocol development would benefit from some bad latency =], that's what you should be building it for. |
Fair comment. Happy to close. |
Now, if you do think this is actually important, we could do a Singapore node IN ADDITION to the Hong Kong one more easily. My question though would be, would that be specific to this fleet only? And if so, would it be for all stages or just one? |
All good for now, @jakubgs. Thanks for that. |
in reference to waku-org/js-waku#1465 (comment), it seems a better option to launch a node in Singapore instead of Hong Kong for Asia
The text was updated successfully, but these errors were encountered: