Skip to content

docs: link OpenChainBench public Kaia RPC latency benchmark #437

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.

Sign up for GitHub

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

Open
Flotapponnier wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: link OpenChainBench public Kaia RPC latency benchmark #437

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/references/public-en.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,10 @@ Hence, the main benefit of using an existing Public EN is that it allows you to
- If traffic is concentrated on certain nodes, you may experience service delay.
- To prevent too many requests, rate limits may apply on a per-node basis, which are subject to change without prior notification.

## Public Latency Benchmarks

For a neutral cross-check of the public endpoints listed below, [OpenChainBench](https://openchainbench.com/benchmarks/kaia-rpc) publishes continuous latency measurements for Kaia's keyless JSON-RPC providers. Probes run every 60 seconds from three regions (Paris, Virginia, Singapore) against `eth_getBlockByNumber`, and the harness is open source at [github.com/ChainBench/openchainbench](https://github.com/ChainBench/openchainbench).

## Public JSON-RPC Endpoints

Below is the list of the network domains offered by Kaia’s Public Node Providers.
Expand Down
Loading