FORESHOCK

Protocols

Request coverage

Every protocol here carries a dated score and the share of it backed by independently verified evidence. Where that share is still thin the assessment says so, is marked Low-signal rather than given a risk band, and holds every unevidenced category at the neutral midpoint instead of assuming it safe. Every score and its reasoning are free to read; the underlying dependency, incident and audit records are part of a plan. Each reading here is fixed at the date beside it. Re-scoring never stops, but a changed reading reaches plan holders on the day it changes rather than this page, which is what a plan is for. How a score is built, how to read one, and how the rubric was tested against real exploits are all in the methodology.

Coverage grows three ways: protocols Foreshock selects at its own discretion, protocols requested through the Request coverage button, and sponsored assessments delivered on an agreed timeline. No path has a guaranteed date except sponsorship.

Scores run from 0, the safest reading, to 100, the riskiest, where 50 is the neutral midpoint every unverified category is held at. Red marks a protocol scoring 50 or above, the band called Elevated: worse than neutral on the evidence gathered. Amber marks one below it, called Moderate. The boundary is fixed. It does not move as coverage grows, and it is not fitted to any backtest result.

Ronin Bridge

Ronin Bridge official site N/A

Ethereum

:

  • Evidence: this reading is based on 100% of the scored weight, verified against named sources. Categories without verified data are held at the neutral midpoint at their full weight, never counted as safe.
  • Validation: the rubric is backtested against past exploits of protocols in the same TVL, age and category bucket. None has been evaluated for this one yet, so the reading rests on its evidence alone.

Published 2026-09-25, unchanged since. Subscribers are told the day it changes.

Why this rating
Audit profile17.0
4 audits/contests on record, most recent (Beosin, 2024-08-24) has unread findings, scored as unknown, not assumed clean; has an unresolved critical finding (hard floor applied).
Historical incidents13.5
This protocol has 2 prior incidents of its own, hard floor applied regardless of current size/age.
Code characteristics11.3
Admin key: an unidentified controlling contract (no single key can act alone; its signers and any delay are unverified), upgradeable without a meaningful timelock, open source.
Governance attack surface7.0
No governance token, and the controlling address could not be resolved, so this is scored as though control sits with an identified party. Immutability is only ever established by reading a contract with no owner and no upgrade path, never by failing to find one, so an unresolved controller is treated as a controller.
TVL profile6.5
TVL is 99% below this protocol's own peak and has not recovered, so the revenue that funds audits, bounties and maintenance is largely gone while the contracts still hold value; TVL change (9%) is within a stable range.
Dependency risk6.0
Uses 1 oracle. No price oracle: the gateway is a 1:1 lock/mint custody bridge, not a price-dependent one.
Show the evidenceSecurity rests on the bridge-operator multi-signature scheme described in Ronin's own docs ("a multi-signature bridge, which means that when you make a transaction, multiple bridge operators have to approve it before it's finalized") and in axieinfinity/ronin-smart-contracts' own README ("the validators simply provide a signature that the withdrawal event has taken place. The withdrawal then needs to collect enough signatures before it can be claimed by the user on Ethereum"). bridges_relied_on is [] because the audited MainchainGatewayV2/V3 contracts (see audit_data.json) are this protocol's own canonical mainchain gateway, not a dependency on another bridge. Ronin's primary consumer-facing bridging path was migrated to Chainlink CCIP, completed April 2025 per Ronin's own blog (blog.roninchain.com/p/the-ronin-bridge-chainlink-ccip-migration), and none of the four audits on file cover CCIP; that migration is recorded here as context, not as a bridges_relied_on dependency of the gateway contract this entry describes, since the CCIP lanes are a separate, newer bridging path rather than something the audited MainchainGatewayV3 contract itself calls into.
Team factors1.7
Doxxed team, track record: unknown.
Protocol age1.5
1550 days live, past the ~1yr floor; treated the same as any older protocol, not scored progressively safer with more age.
Bug bounty1.0
Has a bug bounty program, up to $1 000 000.
Assets held (2)

Available with a plan. See pricing.

Dependencies (1)

Available with a plan. See pricing.

Incident history (2)

Available with a plan. See pricing.

Audit history (5)

Available with a plan. See pricing.

Common questions about Ronin Bridge

Foreshock's independent reading of Ronin Bridge is Elevated risk, 65.5 out of 100, as of 25 September 2026. The largest single contributor to that reading is audit profile: 4 audits/contests on record, most recent (Beosin, 2024-08-24) has unread findings, scored as unknown, not assumed clean; has an unresolved critical finding (hard floor applied). All nine scored categories are backed by verified evidence. This published reading is fixed at that date. Re-scoring never stops, and when a reading changes it reaches plan holders on the day it changes rather than this page. Foreshock publishes the reading and the reasoning behind it. It is not a verdict on whether to use this protocol, and it is not investment advice.

Is Ronin Bridge safe?
Foreshock does not answer that as a yes or a no. Its independent reading of Ronin Bridge is Elevated risk, 65.5 out of 100, as of 25 September 2026, led by audit profile: 4 audits/contests on record, most recent (Beosin, 2024-08-24) has unread findings, scored as unknown, not assumed clean; has an unresolved critical finding (hard floor applied). The score and the reasoning are published in full so the reading can be checked rather than trusted.
Has Ronin Bridge been audited?
4 audits/contests on record, most recent (Beosin, 2024-08-24) has unread findings, scored as unknown, not assumed clean; has an unresolved critical finding (hard floor applied). An audit describes the code at the time it was reviewed. It is not a statement that the protocol is safe today.
Who controls Ronin Bridge?
Admin key: an unidentified controlling contract (no single key can act alone; its signers and any delay are unverified), upgradeable without a meaningful timelock, open source. No governance token, and the controlling address could not be resolved, so this is scored as though control sits with an identified party. Immutability is only ever established by reading a contract with no owner and no upgrade path, never by failing to find one, so an unresolved controller is treated as a controller.
Has Ronin Bridge been exploited before?
This protocol has 2 prior incidents of its own, hard floor applied regardless of current size/age. Foreshock records an incident against a protocol whether it originated there or was inherited from something it depends on.
When was this Ronin Bridge assessment last updated?
25 September 2026, and that date does not move on its own. A reading published here is fixed when it is published; re-scoring never stops, and a changed reading reaches plan holders on the day it changes rather than this page. Every category carries the date of the evidence behind it.
Also covered on Ethereum

This assessment follows Foreshock's published methodology. Exact category weights, scoring rules, thresholds, and aggregation logic are proprietary and not shown here. How to interpret this assessment

This reading will change.

This reading is fixed at the date above it, and it stays there. We keep re-scoring Ronin Bridge as the evidence moves, a new audit, a changed admin control, an incident, and this page is free to read and always will be. The updated reading is what a plan buys: you are told by email on the day it changes, instead of finding out the next time you happen to look.

Pick one protocol and get a free weekly summary of what changed. Same-day alerts come with a plan.

Monitor this protocolGet told when this changesBrowse every protocol