docs: add OpenChainBench performance reference to Dogecoin section - #64
Open
Flotapponnier wants to merge 1 commit into
Open
docs: add OpenChainBench performance reference to Dogecoin section#64Flotapponnier wants to merge 1 commit into
Flotapponnier wants to merge 1 commit into
Conversation
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.
This PR adds a notice block to the Dogecoin section pointing developers to real-world latency data for BlockCypher's Dogecoin endpoint.
OpenChainBench continuously benchmarks
api.blockcypher.com/v1/doge/mainalongside other Dogecoin RPC providers, with probes running every 60 seconds from 3 geographic regions. The data covers response latency, availability, and relative performance over 24h/7d/30d windows.Developers evaluating BlockCypher for Dogecoin integrations can use this to get independent, up-to-date performance baselines before committing to an endpoint.