docs: add OpenChainBench live RPC benchmark

[Flotapponnier]

Adds a reference to OpenChainBench, which independently tracks Lisk RPC providers on latency (p50, p99) and success rates from 3 global regions, updated every 60 seconds.

Useful for developers choosing between providers listed on this page.

Summary by CodeRabbit

• Documentation
  • Added benchmark information for Lisk RPC providers, including latency, success rates, regional performance, update frequency, and a link to the full benchmarks.

[coderabbitai]

📝 Walkthrough

Walkthrough

The documentation adds an OpenChainBench section for independent Lisk RPC provider benchmarks. It lists latency, success-rate, regional measurements, update frequency, and a benchmark link.

Changes

OpenChainBench provider documentation

Layer / File(s)	Summary
Document provider benchmarks docs/lisk-chain/lisk-tools/node-providers.md	Adds OpenChainBench benchmark coverage details and a link to the Lisk RPC benchmark.

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

Poem

A rabbit hops through docs so bright,
And maps RPC speeds just right.
Latency measured, regions shown,
Success rates neatly known.
Benchmarks linked with paws held high!

🚥 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 clearly and concisely describes the addition of an OpenChainBench live RPC benchmark reference.
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 `@docs/lisk-chain/lisk-tools/node-providers.md`:
- Line 124: Update the OpenChainBench description to replace “for your users'
location” with “for the probe region closest to your deployment,” accurately
describing the fixed-region benchmark selection.

🪄 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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 44314c34-837b-48bb-9026-a7d180236c17

📥 Commits

Reviewing files that changed from the base of the PR and between 86e9678 and 76695c2.

📒 Files selected for processing (1)

• docs/lisk-chain/lisk-tools/node-providers.md

[coderabbitai]

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Describe region selection precisely.

The benchmark uses fixed probe regions and asks readers to select the region closest to their deployment. The phrase “for your users' location” implies per-user geolocation or personalized ranking. Replace it with “for the probe region closest to your deployment.” (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 `@docs/lisk-chain/lisk-tools/node-providers.md` at line 124, Update the
OpenChainBench description to replace “for your users' location” with “for the
probe region closest to your deployment,” accurately describing the fixed-region
benchmark selection.