From 0c7a9bd046f5357fc2a29ede7ce599a3049c1fb7 Mon Sep 17 00:00:00 2001 From: Florent Tapponnier Date: Sat, 20 Jun 2026 04:59:38 +0200 Subject: [PATCH] feat(bridge-benches): add per-destination chain dimension Adds a 'dimensions.chain' block to bridge-quote-latency and bridge-fee with values matching the harness chain label (Solana / Base / Arbitrum / HyperCore). The site UI surfaces this as clickable tabs. Why: the aggregate cross-corridor view is misleading on bridges with asymmetric per-corridor performance. Near Intents in particular is bimodal (Arb to HyperCore ~30ms via solver-cached bid, Sol to Base ~3000ms full auction wait), and the aggregate histogram quantile produced 175ms p50 which represents neither corridor. Requires the matching mobula-api PR (chain label emission in the bridge-monitor harness). --- benchmarks/bridge-fee.yml | 13 +++++++++++++ benchmarks/bridge-quote-latency.yml | 15 +++++++++++++++ 2 files changed, 28 insertions(+) diff --git a/benchmarks/bridge-fee.yml b/benchmarks/bridge-fee.yml index 550606b3..e096f421 100644 --- a/benchmarks/bridge-fee.yml +++ b/benchmarks/bridge-fee.yml @@ -11,6 +11,19 @@ status: live metric: Effective fee unit: pct +# Per-destination breakdown. Same rationale as bridge-quote-latency: +# bridges quote different cost structures per corridor (gas on the +# destination dominates short hops, solver spread dominates long +# auction routes), so an aggregate cross-corridor cost percent +# obscures more than it reveals. +dimensions: + chain: + - { value: all, label: All destinations } + - { value: Solana, label: To Solana } + - { value: Base, label: To Base } + - { value: Arbitrum, label: To Arbitrum } + - { value: HyperCore, label: To HyperCore } + seo_intro: | This benchmark measures the cheapest cross-chain bridge live, refreshed every five minutes across the major USDC corridors. The headline figure diff --git a/benchmarks/bridge-quote-latency.yml b/benchmarks/bridge-quote-latency.yml index 102978a3..48c033d9 100644 --- a/benchmarks/bridge-quote-latency.yml +++ b/benchmarks/bridge-quote-latency.yml @@ -11,6 +11,21 @@ status: live metric: Quote latency unit: ms +# Per-destination breakdown. The bridge-monitor harness emits the chain +# label set to route.ToChain (capitalized). Each bridge has wildly +# different per-corridor latency profiles (Near Intents in particular is +# bimodal: solver-cached corridors return in ~30ms while uncached ones +# wait the full 3s solver auction window) so aggregating across all +# destinations produces meaningless cross-corridor averages. The "All" +# tab keeps the aggregate view; the per-chain tabs reveal the truth. +dimensions: + chain: + - { value: all, label: All destinations } + - { value: Solana, label: To Solana } + - { value: Base, label: To Base } + - { value: Arbitrum, label: To Arbitrum } + - { value: HyperCore, label: To HyperCore } + seo_intro: | This benchmark measures how fast each cross-chain bridge quote API returns a usable response, the response-time half of the bridge story