Skip to content

the bridge bench overran both snippet limits, so the engine chose the trim #2776

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Flotapponnier merged 1 commit into from
Oct 2, 2026
Merged

the bridge bench overran both snippet limits, so the engine chose the trim #2776

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions benchmarks/bridge-execution-latency.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,8 @@
slug: bridge-execution-latency
number: "261"
title: "Fastest on-chain bridge execution: real settlement latency, Mobula vs Relay vs LI.FI vs Near Intents"
seo_title: "Fastest bridge execution 2026: real on-chain settlement latency and success rate"
seo_description: "Live on-chain bridge execution, not quotes: real millisecond settlement latency, success rate and realized fees for Mobula, Relay, LI.FI and Near Intents on a self-conserving USDC triangle across Solana, Base and Arbitrum."
seo_title: "Fastest bridge 2026: real on-chain settlement latency"
seo_description: "Real bridge executions, not quotes: settlement latency, success rate and realized fees for Mobula, Relay, LI.FI and Near Intents."
subtitle: Real on-chain settlement latency (deposit included to credit observed, ms), success rate and realized fees for executed bridge transactions on a self-conserving USDC triangle (Solana, Base, Arbitrum), at $3 and $30, measured from EU-West.
category: Bridges
status: live
Expand Down
Loading