add osmosis-rpc bench (091) + register Osmosis chain - #1336
Merged
Conversation
…DK chain in the RPC cluster
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.
First Cosmos SDK chain in the RPC latency cluster. Ships:
Site
src/lib/chains.ts— registerosmosis(L1, OSMO native, CometBFT consensus)src/lib/logo-manifest.ts— aliasosmosis-official→osmosislogosrc/data/provider-registry.ts— new entries for osmosis-official, polkachu, imperator, lavenderfive (publicnode + onfinality already registered)src/lib/spec.ts— bump cache keys v37/v40 (new bench in set)Bench spec
benchmarks/osmosis-rpc.yml(bench 091) — mirror of polkadot-rpc pattern, 5-provider launch cohort with per-region breakdownsHarness
harnesses/rpc-capabilities/cmd/script/config.go— newKind: "cosmos", 5-provider matrix underosmosisharnesses/rpc-capabilities/cmd/script/probe.go—callCosmosStatus(TendermintstatusPOST, decimal height parsing),cosmosStaleBlockGap, dispatch wired in probeOne, cosmos added to the no-consensus-participation list for v1Live-audited 2026-07-23: 5 no-key providers pass the
statusprobe (Osmosis Foundation, Polkachu, PublicNode, Imperator, LavenderFive). Excluded: Lava (403 without key), OnFinality (timing out), Numia (401), and several community endpoints that returned connect errors — full audit list in the bench methodology.Harness deploy on the VPS (ocb-par-main) is a follow-up: this PR is site + spec + harness code only, so once merged the bench renders in draft on staging until the Prom scrape kicks in.