-
Notifications
You must be signed in to change notification settings - Fork 16
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
Change mainnet TFChain RPC node endpoint URL's #2495
Comments
We need to keep the records to work too |
so in the end zos should use these 5 tfchain public rpc endpoints:
|
Why can't we also keep the old records working? |
because: instead of spending time/money on setting these up again, we opted to utilize the 5 public rpc endpoints we have already running from the grid backend stacks (above list) since there is much confusion about how our current setup is, it seemed logic to also leave out 02 if we leave out 03 and 04. Otherwise a question comes 'where are the other numbered endpoints?'. We where told to use land codes, so here we are. |
@xmonader could you elaborate why it's an issue to change the url's? |
We currently use 4 URLs tfchain.grid.tf which are 4 hetzner servers + 02 03 04 servers which are standalone nodes. The latter was set up in the beginning to provide some redundancy in the tfchain endpoints. Since we now have multiple docker compose backend stacks, which each hosts a full TFChain node, it no longer makes sense from an operations perspective to keep maintaining separate stand-alone nodes.
02, 03 and 04.tfchain.grid.tf should be removed and tfchain.{fin, be, sg, us}.grid.tf should be added. The original tfchain.grid.tf should stay.
The text was updated successfully, but these errors were encountered: