Repository navigation
release: Route on benches 033 and 102, measured from our own probes - #3028
Merged
Merged
Conversation
…rage (#3025) Adds Robinhood Chain (0.1 ETH -> USDG) to the evm-swap-quoting basket, probed by Route, KyberSwap and LI.FI, and a Route adapter to token-quote-coverage. Route adapters only register when ROUTE_API_KEY is set. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
bakabhai993
pushed a commit
to bakabhai993/OpenChainBench
that referenced
this pull request
Oct 18, 2026
Route went to main as a cherry-pick (ChainBench#3028, 45faeaf) so it could ship without waiting for the release. dev carries the same change under its own SHA, so git sees two unrelated commits touching the same lines and ChainBench#3021 went from clean to CONFLICTING. One file conflicts, benchmarks/evm-quote-latency.yml, and it is not a disagreement. Checked line by line before resolving: every non-blank line on main is present on dev, and dev adds 80 that main does not have, which is exactly the eight providers times ten lines of regions blocks from ChainBench#3032. dev is a strict superset, so the resolution takes dev's side whole. token-quote-coverage.yml auto-merged with no help. Gates on the merge result: 253 specs valid, tsc clean, 597 tests pass.
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
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.
Cherry-pick of #3025 onto
main, so Route reaches production without waiting for the rest of the release.Measured from our own probes before opening this, which is the point of the sequence rather than a formality. us-east, the pair the PR adds, 0.1 ETH → USDG on Robinhood Chain:
Their own figures said 99–141 ms against 284–478 and 448–1,446. Ours land in the same order, which is worth saying plainly: the submission was accurate. It is still our number that ships.
Already live on
dev's infrastructure, deployed before this PR:ROUTE_API_KEYset onevm-quote-latency-us,-euand-sgp, piped from the secrets directory so it never reached a command line. All three redeployed at dev HEAD and reporting8 providers,rotating 6-pair basket,Route key set: true.ocb-token-quote-coveragerebuilt on the VPS and restarted with the key, now logging[probe] route robinhood/... -> HIT.One conflict in the cherry-pick, in
token-quote-coverage.yml:mainsays four quote sources cover Robinhood, the PR says five. Resolved on the PR's paragraph, since Route is the fifth and that is the change.Gates on this branch: 245 specs valid, tsc clean, 505 tests,
go buildandgo veton both harnesses, and a fullnext buildgenerating 287 static pages.Not in this cherry-pick, deliberately: the basket going from five pairs to six drops every existing (provider, chain) from 288 to 240 samples per 24h. That rides along in the harness code, which is already deployed, but it is a methodology change to a published board and deserves its own note rather than being buried here.