docs: link OpenChainBench public Neutron RPC latency benchmark - #313
Open
Flotapponnier wants to merge 1 commit into
Open
docs: link OpenChainBench public Neutron RPC latency benchmark#313Flotapponnier wants to merge 1 commit into
Flotapponnier wants to merge 1 commit into
Conversation
Author
|
Just bumping this in case it got buried under other PRs. Happy to adjust the wording or placement if that would help! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds a short section on
resources/endpoints.mdxlinking to OpenChainBench's public latency dashboard for Neutron RPC providers.OpenChainBench (OCB) is an open-source, multi-region latency benchmark for public RPC endpoints. For Neutron it probes the Tendermint
statusmethod every 60 seconds from Paris (eu-west), Virginia (us-east), and Singapore (ap-southeast) against three keyless providers currently in scope (PublicNode, Polkachu, LavenderFive).Intended as a neutral cross-check for integrators alongside the existing
status.cosmos.directory/neutronlink. Note:rpc-kralum.neutron-1.neutron.orgreturned an SSL handshake failure during the launch audit and was excluded — happy to re-audit once TLS is fixed.Precedent: similar additions on osmosis-labs/docs#349 and jup-ag/docs#939.