diff --git a/benchmarks/blast-rpc.yml b/benchmarks/blast-rpc.yml index 899b7b0e..3a75a2a5 100644 --- a/benchmarks/blast-rpc.yml +++ b/benchmarks/blast-rpc.yml @@ -30,7 +30,7 @@ methodology: findings: - "{{best_name}} currently leads free Blast RPC at {{best_p50}} (`eth_getBlockByNumber` p50, 24h) across 4 measured providers." - - "`rpc.blast.io` posts ~2 ms in every region simultaneously. On-chain response headers confirm geo-distributed nodes: `blast_blast-mainnet_fra` from eu-west, `blast_blast-mainnet_sin` from Singapore, a US node from us-east. Blast runs RPC nodes inside the same GCP datacenters as our Railway probes, producing sub-2 ms figures that reflect co-located infrastructure rather than typical user latency. A user in Paris reaches the Frankfurt node in ~40 ms; a user outside GCP will see 30-100 ms depending on location. Heads are fresh per stale detection." + - "`rpc.blast.io` posts ~2 ms in every region. Response headers confirm geo-distributed GCP nodes co-located with our Railway probes (`blast_blast-mainnet_fra` from eu-west, `blast_blast-mainnet_sin` from Singapore, US node from us-east). Sub-2 ms reflects co-location, not real-world latency; outside GCP expect 30-100 ms. Heads are fresh per stale detection." - "{{name:drpc}} ({{p50:drpc}}) is the honest-infrastructure comparison point: anycast consistency across the three regions with real node round trips behind it, the profile that wins it 10 of the 12 expansion chains." - "{{name:tenderly}} sits at the expansion's familiar flat ~330 ms in all regions on Blast, single-origin routing on a gateway that is genuinely quick on the major chains." @@ -44,7 +44,7 @@ faq: - q: "How is Blast RPC latency measured here?" a: "One identical JSON-RPC POST (`eth_getBlockByNumber`) every 60 seconds against each provider from each of 3 regions, with the same plain HTTP client. Wall-clock round-trip is recorded at millisecond precision; p50/p90/p99 are computed via Prometheus `quantile_over_time` over 24 hours. Responses are classified (`ok` / `http_err` / `jsonrpc_err` / `stale` / `timeout`) so an endpoint stuck on an old head or returning errors behind HTTP 200 is never ranked as fastest. The harness is open source and every number on this page is a public Prometheus query you can run yourself." - q: "Is rpc.blast.io really that fast, or is something else going on?" - a: "Blast runs geo-distributed RPC nodes inside major cloud datacenters (GCP us-east, GCP europe-west4/Frankfurt, GCP asia-southeast1/Singapore). Our Railway probes run in the same three GCP regions, so each probe hits the co-located Blast node with a sub-LAN round trip. The `x-node-id` response header confirms this: `blast_blast-mainnet_fra` from eu-west, `blast_blast-mainnet_sin` from Singapore. The blocks are fresh — this is not a cache hit — but the 1-2 ms figure reflects network co-location, not what a developer outside GCP infra will experience. From a typical residential connection or a non-GCP cloud, expect 30-100 ms." + a: "Blast runs geo-distributed RPC nodes inside major cloud datacenters (GCP us-east, GCP europe-west4/Frankfurt, GCP asia-southeast1/Singapore). Our Railway probes run in the same three GCP regions, so each probe hits the co-located Blast node with a sub-LAN round trip. The `x-node-id` response header confirms this: `blast_blast-mainnet_fra` from eu-west, `blast_blast-mainnet_sin` from Singapore. The blocks are fresh (not a cache hit) but the 1-2 ms figure reflects network co-location, not what a developer outside GCP infra will experience. From a typical residential connection or a non-GCP cloud, expect 30-100 ms." source: https://github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities diff --git a/benchmarks/monad-rpc.yml b/benchmarks/monad-rpc.yml index 0f4885d8..3f0581da 100644 --- a/benchmarks/monad-rpc.yml +++ b/benchmarks/monad-rpc.yml @@ -47,7 +47,7 @@ methodology: findings: - "{{best_name}} currently leads the free Monad RPC field at {{best_p50}} (p50, 24h) across 5 measured providers." - - "{{name:monad-official}} answers at {{p50:monad-official}}. On-chain response headers (`x-node-id: monad_monad-mainnet_fra`) confirm geo-distributed nodes co-located with our Railway probes in GCP datacenters (Frankfurt for eu-west, equivalent US and Singapore nodes). The sub-2 ms figure reflects network co-location, not what a developer outside GCP infra will experience — expect 30-120 ms from a typical connection. Rate-limit: 25 rps." + - "{{name:monad-official}} answers at {{p50:monad-official}}. On-chain response headers (`x-node-id: monad_monad-mainnet_fra`) confirm geo-distributed nodes co-located with our Railway probes in GCP datacenters (Frankfurt for eu-west, equivalent US and Singapore nodes). The sub-2 ms figure reflects network co-location, not what a developer outside GCP infra will experience; expect 30-120 ms from a typical connection. Rate-limit: 25 rps." - "{{name:drpc}} sits at {{p50:drpc}} and {{name:tenderly}} at {{p50:tenderly}}: the multi-chain gateways reached Monad within weeks of mainnet, but route through their global meshes rather than chain-local nodes." - "{{name:bloxroute}} at {{p50:bloxroute}} is the outlier entry: a BDN operator exposing a keyless endpoint, unusual for a company whose core product is paid low-latency access." diff --git a/benchmarks/perp-cost-slope.yml b/benchmarks/perp-cost-slope.yml index f8787ac6..a1b83ba2 100644 --- a/benchmarks/perp-cost-slope.yml +++ b/benchmarks/perp-cost-slope.yml @@ -88,7 +88,7 @@ per_chain_explainer: findings: - "{{name:gains}} and {{name:gmx}} always score 1.00 by construction, not by performance: oracle-priced venues charge a flat percentage of notional with no orderbook, so the $1M all-in is identical to the $1k all-in in basis points regardless of market conditions. Their top leaderboard position reflects fee structure, not execution quality." - - "Among orderbook venues, {{name:hyperliquid}} sits at {{p50:hyperliquid}} cost slope (24h avg) — the lowest impact in the cohort at $1M notional, driven by the deepest onchain book." + - "Among orderbook venues, {{name:hyperliquid}} sits at {{p50:hyperliquid}} cost slope (24h avg), the lowest impact in the cohort at $1M notional, driven by the deepest onchain book." - "Venues showing N/A in the slope column cannot reliably fill a $1M market order. The fill-rate panel shows what fraction of measurement cycles the $1M tier was successfully absorbed." - "The cost slope is asset-specific: use the chain tabs to compare ETH (deepest books), BTC (tightest books) and SOL (thinnest books) separately." diff --git a/benchmarks/trading-app-execution.yml b/benchmarks/trading-app-execution.yml index 227c77cd..a4c2f2f9 100644 --- a/benchmarks/trading-app-execution.yml +++ b/benchmarks/trading-app-execution.yml @@ -57,6 +57,24 @@ faq: - q: "Which platforms are tracked on EVM chains?" a: "GMGN, Maestro, and Banana Gun are tracked on Ethereum. GMGN, Maestro, Axiom, and Banana Gun are tracked on BSC. GMGN, Maestro, and Banana Gun are tracked on Base. pump.fun Terminal is tracked on all three EVM chains." +providers: + - slug: axiom + name: Axiom + - slug: gmgn + name: GMGN + - slug: trojan + name: Trojan + - slug: maestro + name: Maestro + - slug: pump-fun + name: pump.fun + - slug: photon + name: Photon + - slug: bullx + name: BullX + - slug: banana-gun + name: Banana Gun + # No prometheus section -- this bench uses a custom page renderer # at src/app/benchmarks/trading-app-execution/page.tsx that reads # directly from the exec REST API (exec.openchainbench.com). diff --git a/src/app/apps/exec/page.tsx b/src/app/apps/exec/page.tsx deleted file mode 100644 index bc5cb0ec..00000000 --- a/src/app/apps/exec/page.tsx +++ /dev/null @@ -1,77 +0,0 @@ -import type { Metadata } from "next"; -import { pageMetadata } from "@/lib/page-metadata"; -import { safeJsonLd, buildBreadcrumbJsonLd } from "@/lib/jsonld"; -import { SITE } from "@/data/site"; -import { fetchExecLeaderboard } from "@/lib/solana-exec"; -import { SolanaExecTable } from "@/components/solana-exec-table"; - -const DESCRIPTION = - "Solana trading platform execution quality: priority fees, Jito bundle rates, and platform fees — measured passively from on-chain data. Updated every hour."; - -export const metadata: Metadata = pageMetadata({ - path: "/apps/exec", - title: "Solana Execution Quality — pump.fun, FOMO, Axiom, GMGN | OpenChainBench", - description: DESCRIPTION, -}); - -export const revalidate = 60; - -export default async function SolanaExecPage() { - const data = await fetchExecLeaderboard(); - - const breadcrumb = { - "@context": "https://schema.org", - ...buildBreadcrumbJsonLd([ - { name: "Home", item: SITE.url }, - { name: "Apps", item: `${SITE.url}/apps` }, - { name: "Solana Execution", item: `${SITE.url}/apps/exec` }, - ]), - }; - - return ( -
-