Repository navigation
feat(staging): add 4 production-ready benchmarks to dev only - #740
Merged
Merged
Conversation
After dev → main reconciliation (PRs A-E), dev was hard-reset to main. This commit re-introduces the 4 production-ready benchmarks that lived on the old dev branch as staging-only content. They will NOT be promoted to main until they pass staging review. Benches: - bridge-revenue.yml (188L, status: live) — bridge revenue tracking - evm-quote-latency.yml (194L, status: live) — EVM aggregator quote latency (Mobula vs Codex vs GeckoTerminal etc.) - solana-dex-quote-latency.yml (192L, status: live) — Solana DEX quote latency (Jupiter vs Mobula vs others) - solana-tx-landing.yml (218L, status: live) — Solana tx landing benchmark Companion editorial content (for SEO long-tail): - answers/which-evm-aggregator-has-the-fastest-quote.yml - answers/which-solana-dex-aggregator-is-the-fastest.yml - alternatives/jupiter.yml Workflow going forward: - main = prod (openchainbench.com), source of truth - dev = staging buffer (auto-deploy to staging Preview URL) - These 4 benches live on dev. When approved, open a dedicated PR cherry-picking them to main. - Future feature work: open a feature branch from dev (or main), PR to dev for staging review, then promote to main.
bakabhai993
pushed a commit
to bakabhai993/OpenChainBench
that referenced
this pull request
Sep 12, 2026
…hainBench#740) After dev → main reconciliation (PRs A-E), dev was hard-reset to main. This commit re-introduces the 4 production-ready benchmarks that lived on the old dev branch as staging-only content. They will NOT be promoted to main until they pass staging review. Benches: - bridge-revenue.yml (188L, status: live) — bridge revenue tracking - evm-quote-latency.yml (194L, status: live) — EVM aggregator quote latency (Mobula vs Codex vs GeckoTerminal etc.) - solana-dex-quote-latency.yml (192L, status: live) — Solana DEX quote latency (Jupiter vs Mobula vs others) - solana-tx-landing.yml (218L, status: live) — Solana tx landing benchmark Companion editorial content (for SEO long-tail): - answers/which-evm-aggregator-has-the-fastest-quote.yml - answers/which-solana-dex-aggregator-is-the-fastest.yml - alternatives/jupiter.yml Workflow going forward: - main = prod (openchainbench.com), source of truth - dev = staging buffer (auto-deploy to staging Preview URL) - These 4 benches live on dev. When approved, open a dedicated PR cherry-picking them to main. - Future feature work: open a feature branch from dev (or main), PR to dev for staging review, then promote to main. Co-authored-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
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.
Re-introduces the 4 production-ready benchmarks that lived on the old dev (now archived as dev-archive-2026-06-26) as staging-only content. They stay on dev until promoted via a separate PR to main.
Backed up dev state in branch dev-archive-2026-06-26 before this.