Arbitrum canonical bridge: cross-chain bridges rating breakdown
There is no committee. Your withdrawal is secured by Ethereum itself through the fraud-proof system, and the seven-day challenge window is not a delay you are suffering — it is the window in which a fraudulent withdrawal can be proven and stopped. Nobody attests to anything on your behalf. No bridge validator set exists to be compromised, because there is no bridge validator set.
There is no committee. Your withdrawal is secured by Ethereum itself through the fraud-proof system, and the seven-day challenge window is not a delay you are suffering — it is the window in which a fraudulent withdrawal can be proven and stopped. Nobody attests to anything on your behalf.
How the score is built
Each criterion is scored 0–10 and weighted. The median column is the middle score across every entry in this ranking, so a row reads as a position rather than a number.
| Criterion | What we measured | Weight | Score | Category median | Rank | Weighted gap |
|---|---|---|---|---|---|---|
| Trust assumption | — | 40% | 10 | 4 | 1 of 16 | +2.40 |
| The upgrade key | Security Council, 9-of-12 emergency upgrade · sourced · 2026-07-15 · source | 15% | 7 | 3 | 1 of 16 | +0.60 |
| Incidents — and did users get paid | — | 25% | 10 | 9 | 1 of 16 | +0.25 |
| Audits and transparency | — | 10% | 8 | 5.5 | 1 of 16 | +0.25 |
| Cost and speed | roughly 15–30 minutes depending on congestion, no challenge window deposit time · published · 2026-07-15 · source | 10% | 9 | 6 | 1 of 16 | +0.30 |
Measured 15 July 2026 · weights and method · decided by trust assumption, worth +2.40 points against the median
Trust assumption: 10/10
Not a label — a number. Who, exactly, can move the money if they collude or are compromised? A canonical rollup bridge answers "nobody: Ethereum itself verifies the withdrawal, and the seven-day window is the period in which fraud can be proven". An external committee answers with a threshold, and that threshold IS the rating: Ronin was 5-of-9 and four of those keys sat on one company's servers. Harmony was 2-of-5. We publish the signer count and the threshold wherever they exist, and where a project will not state them, that silence is scored as the risk it is.
Scored 10 of 10 against a category median of 4, which places it 1st of 16 among cross-chain bridges on this criterion. At a 40% weight that is 2.40 points above the median contribution of the weighted total. The best score in the category is 10, the worst 2.
The upgrade key: 7/10
The assumption that quietly overrides the whitepaper. A bridge whose contracts can be upgraded by a small multisig HAS that multisig as its real trust model, whatever the architecture diagram says — and Nomad proves it: the bug that lost $186m was introduced BY an upgrade. So we ask who holds upgrade authority, and we score the answer rather than the design.
Scored 7 of 10 against a category median of 3, which places it 1st of 16 among cross-chain bridges on this criterion. At a 15% weight that is 0.60 points above the median contribution of the weighted total. The best score in the category is 7, the worst 1.
Incidents — and did users get paid: 10/10
Every exploit with its root cause, and then the column nobody else publishes: were users made whole, and is that INDEPENDENTLY confirmed or merely claimed? Read the results carefully, because they do not mean what people think. Reimbursement in this category has tracked the sponsor’s balance sheet, not the bridge’s security. That makes "they paid people back last time" close to worthless as a safety signal, and we score it accordingly.
Scored 10 of 10 against a category median of 9, which places it 1st of 16 among cross-chain bridges on this criterion. At a 25% weight that is 0.25 points above the median contribution of the weighted total. The best score in the category is 10, the worst 3.
Audits and transparency: 8/10
Named firms, dated reports, published. An unnamed audit is not an audit. Undisclosed validator counts are scored as undisclosed, not assumed benign.
Scored 8 of 10 against a category median of 5.5, which places it 1st of 16 among cross-chain bridges on this criterion. At a 10% weight that is 0.25 points above the median contribution of the weighted total. The best score in the category is 8, the worst 4.
Cost and speed: 9/10
Deliberately the smallest weight, and one qualification matters more than the number: we refuse to treat the canonical bridge’s seven-day withdrawal window as a defect. It is not a delay that clever engineering removed — it is the exact period during which Ethereum can be used to prove a withdrawal fraudulent. A fast bridge is fast for one reason: it substituted somebody’s signature for that proof.
Scored 9 of 10 against a category median of 6, which places it 1st of 16 among cross-chain bridges on this criterion. At a 10% weight that is 0.30 points above the median contribution of the weighted total. The best score in the category is 9, the worst 5.
Other measurements
Its nearest neighbours in this ranking
| # | Entry | Trust assumption | How it differs |
|---|---|---|---|
| 2 | Optimism / Base canonical bridges (OP Stack) | 10 | Level on trust assumption; the gap is elsewhere. |
| 3 | Circle CCTP | 8 | Behind by 2 on trust assumption. |
Questions about this score
Why does withdrawing from Arbitrum take seven days?
+
Because that window is the security. It is the period during which anyone can prove to Ethereum that a withdrawal is fraudulent and stop it. A bridge that gives you the money immediately has not solved the delay — it has replaced the proof with a signature from a group you now have to trust, or with a relayer taking the risk on your behalf for a fee.
Should I ever use a third-party bridge into Arbitrum?
+
For deposits, no — the canonical bridge takes minutes and has no challenge window, so there is nothing to gain. For withdrawals, a fast bridge is a real service if seven days is genuinely unacceptable, provided you understand you are paying someone to take the settlement risk you would otherwise carry.