Bridge entity

Ronin Bridge

Ronin Bridge is the bridge associated with the Ronin network. BIR records the March 2022 validator-key compromise and the distinct August 2024 bridge-upgrade incident in which operator-weight initialization failed, enabling temporary unauthorized withdrawals that were returned by whitehat/MEV actors before the vulnerability was fixed and independently audited.

activereviewedcurrent

Bridge facts

Canonical name
Ronin Bridge
Type
Asset Bridge
Status
Active
Confidence
High
Primary chains
Ronin, Ethereum
Primary assets
ETH, USDC
Operator
Sky Mavis
Ecosystem
Ronin
Launch date
Unknown
End date
Unknown
Terminal reason
Not applicable / unknown
Last reviewed
2026-09-04
Last verified
2026-09-04

Incident cases

  • Ronin Bridge 2024 operator-weight initialization incident2024-08-06

    On August 6, 2024, a Ronin Bridge upgrade left bridge-operator weight parameters uninitialized, causing the withdrawal authorization threshold to be misinterpreted. Whitehat/MEV actors temporarily withdrew approximately 4,000 ETH and 2 million USDC, the bridge was paused, the assets were returned, and a recovery proposal restored the operator weights. A Ronin-hosted Beosin audit later verified that fake-credential withdrawals failed after the fix.

    Security Misconfiguration4,000 ETH + 2M USDC temporarily withdrawn; returnedFinal outcome known
  • Ronin Bridge validator-key compromise2022-03-29

    In March 2022, Ronin Bridge was exploited after validator keys were compromised, leading to one of the largest reported bridge losses in crypto history. The incident later became a reference case for bridge validator and cross-chain security risk.

    Exploit$620 millionFinal outcome known

Evidence records

Official URL status

Official URL recorded as live: https://bridge.roninchain.com/
Independent incident archive

Help maintain bridge history

Support incident linkage, lifecycle updates, evidence preservation, broken-link replacement, and corrections.

Support BIR
Record maintenance

Report a correction

Report missing evidence, incorrect dates, outcome changes, recovery details, reimbursement status, or broken links. GitHub Issues are preferred for structured review; the Google Form is available if you do not use GitHub.