docs: link OpenChainBench public Injective RPC latency benchmark

[Flotapponnier]

Summary

Adds a short section to Public Endpoints linking to OpenChainBench, a public, open-source latency benchmark for Injective's Tendermint RPC providers. It probes the Injective Foundation endpoint and community providers (PublicNode, Polkachu, LavenderFive) every 60s from three regions (Paris, Virginia, Singapore) using the status method.

Intended as a neutral cross-check for integrators picking between the free public RPC options already listed on this page.

Source and methodology are open: https://github.com/ChainBench/openchainbench

Precedent for this kind of addition:

• docs(endpoints): link OpenChainBench public RPC latency benchmark osmosis-labs/docs#349
• docs(latency): link OpenChainBench public Solana DEX quote latency benchmark jup-ag/docs#939

Change

• 4 lines added to .gitbook/infra/public-endpoints.mdx under a new ## Public latency benchmarks heading.
• No endpoint changes, no removals.

Summary by CodeRabbit

• Documentation
  • Added a “Public latency benchmarks” section describing continuous Tendermint status latency measurements.
  • Included benchmark frequency, probe locations, participating providers, and links to the source and methodology repository.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: cf71430f-d5d6-470b-a5c3-fe8a35c67164

📥 Commits

Reviewing files that changed from the base of the PR and between 5ebb0ef and 43fe357.

📒 Files selected for processing (1)

• .gitbook/infra/public-endpoints.mdx

---

📝 Walkthrough

Walkthrough

Adds documentation for continuous OpenChainBench latency benchmarks covering the Injective RPC status method, including probe frequency, geographic locations, and source methodology.

Changes

Public latency benchmarks

Layer / File(s)	Summary
Benchmark documentation .gitbook/infra/public-endpoints.mdx	Adds benchmark provenance, probe cadence, geographic regions, and a source/methodology link for public RPC latency measurements.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the docs update linking the OpenChainBench Injective RPC latency benchmark.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.gitbook/infra/public-endpoints.mdx:
- Line 60: Update the OpenChainBench probe-region description in the public
Injective RPC provider section to replace “Paris” with “Amsterdam,” preserving
Virginia and Singapore.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 09325033-4e33-4bad-898c-cf3faddaf219

📥 Commits

Reviewing files that changed from the base of the PR and between 1a31f49 and 5ebb0ef.

📒 Files selected for processing (1)

• .gitbook/infra/public-endpoints.mdx

[coderabbitai]

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Correct the European probe location.

The benchmark methodology identifies the three regions as Virginia, Amsterdam, and Singapore; this sentence incorrectly says Paris. Please replace Paris with Amsterdam or use the canonical labels us-east, eu-west, and sgp. (openchainbench.com)

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.gitbook/infra/public-endpoints.mdx at line 60, Update the OpenChainBench
probe-region description in the public Injective RPC provider section to replace
“Paris” with “Amsterdam,” preserving Virginia and Singapore.

Source: MCP tools