Add Helikon RPC public endpoints for Phala, Khala and HydraDX #10161
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds Helikon public RPC endpoints for Khala, Phala and HydraDX networks.
All endpoints are load balanced with two archive nodes on NVMe drives on a 500Mbps symmetrical network. All services run on owned hardware in a data center in central Istanbul, and are monitored 24/7 at software (node), hardware (disk, CPU, memory) and network level.
Nodes can be viewed on the W3F Telemetry instance, viewable for Khala, Phala and HydraDX.
Helikon is a member of the IBP GeoDNS and provides public RPC endpoints for Kusama, Westend and Polkadot and all system parachains on these relay chains. We also run boot nodes for all the chains mentioned in this PR.
Thanks!