docs(dev/tooling): reference OpenChainBench for third-party MegaETH RPC comparison#81
Open
Flotapponnier wants to merge 1 commit into
Conversation
Signed-off-by: Florent Tapponnier <contact@openchainbench.com>
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
2 participants
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.
Summary
Adds a short paragraph directly under the RPC Providers table in
docs/dev/tooling.md, pointing readers to the OpenChainBench MegaETH RPC benchmark as an independent third-party latency and reliability comparison of the MegaETH RPC providers listed in the table.Why it fits
The current RPC Providers table lists 10 providers (MegaETH Official, Alchemy, QuickNode, Nirvana Labs, dRPC, GlobalStake, Liquify, Dwellir, Envio HyperRPC, Chainstack). Each provider publishes its own performance claims. Given MegaETH's real-time latency positioning (~10ms block times), builders picking an RPC endpoint benefit from a neutral third-party comparison across the same request pattern.
OpenChainBench probes the MegaETH endpoints every minute from three regions (US East, EU West, Singapore), publishes p50/p95/p99 latency, reliability classification, and stale-block detection. Data ships under a CC BY 4.0 license and the Go harness is open source on GitHub. OpenChainBench has no affiliation with any of the listed providers or MegaETH Labs.
Change
One added paragraph directly after the RPC Providers table. No changes to the table itself or any other section.
Disclosure
I am the maintainer of OpenChainBench. Happy to reword, shorten, or drop the reference entirely if it does not fit the docs style guide.