Across vs Socket Protocol

Across leads on 2 of 2 shared benchmarks, Socket Protocol on 0. Across wins on Fastest cross-chain bridge quote API, live ms ranking (567 ms vs 1.75 s), Cheapest cross-chain bridge for USDC at $300 notional (0.20% vs 0.33%).

Read methodology Last measured Window: rolling 24h2 shared benchmarks
Across logo
Across

Optimistic cross-chain bridge by Risk Labs. Intents are filled by relayers who front liquidity on the destination, repaid from a canonical hub pool. Settlement is typically sub-30 seconds on liquid corridors.

Socket Protocol logo
Socket Protocol

Cross-chain interoperability protocol and bridge aggregator. The Socket API routes bridging and swap transactions across major EVM chains via underlying bridges including Across, Stargate, and CCTP.

Side by side measurements

Frequently asked questions

Across vs Socket Protocol: which one is better?

Across and Socket Protocol are compared on 2 shared OpenChainBench benchmarks. Across leads on Fastest cross-chain bridge quote API, live ms ranking. See the live table on this page for every metric.

Which is faster on fastest cross-chain bridge quote api, live ms ranking, Across or Socket Protocol?

On the Fastest cross-chain bridge quote API, live ms ranking benchmark, Across leads at 567 ms versus Socket Protocol at 1.75 s. Live measurement is updated continuously by the OpenChainBench harness.

How is the Across vs Socket Protocol comparison measured?

Every benchmark on this page uses the same open methodology, published at https://openchainbench.com/methodology. Data is CC-BY-4.0. Measurement harnesses are MIT-licensed.

How this pair was selected

A pair is published when all four conditions hold. Both providers run in the same OpenChainBench benchmark for at least seven consecutive days. Each provider has at least 1000 samples in the measurement window. The head to head query has observable third party search demand. Both providers have a public /products/[slug] page on OCB. The full pair ledger is versioned in the public repo so the methodology is externally verifiable.

Live data refreshes via ISR within 60 seconds of a new run. Sources are the same Prometheus queries surfaced on the parent benchmark pages.