[ { "id": "bir_bridge_000001", "slug": "ronin-bridge", "previous_slugs": [], "redirect_from": [], "canonical_name": "Ronin Bridge", "type": "asset_bridge", "status": "active", "summary": "Ronin Bridge is the bridge associated with the Ronin network. It is included because of the March 2022 validator-key compromise and large reported loss, followed by attribution, recovery, and reimbursement-related aftermath.", "confidence": "high", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-11", "last_verified_at": "2026-06-11", "aliases": [ "Ronin Network Bridge" ], "launch_date": null, "launch_date_precision": "unknown", "end_date": null, "end_date_precision": "unknown", "terminal_reason": null, "official_url": "https://bridge.roninchain.com/", "official_domain": "bridge.roninchain.com", "official_url_status": "live", "archived_url": null, "primary_chains": [ "ronin", "ethereum" ], "primary_assets": [ "eth", "usdc" ], "operator_name": "Sky Mavis", "operator_type": "company", "ecosystem_name": "Ronin", "related_protocols": [ "Axie Infinity" ], "brand_history_notes": null, "major_incident_count": 1, "has_unresolved_incident": false, "has_reimbursement_history": true, "successor_id": null, "predecessor_id": null, "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "Seed record focused on the 2022 incident and aftermath rather than live bridge safety.", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/ronin-bridge/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "id": "bir_bridge_000002", "slug": "wormhole", "previous_slugs": [], "redirect_from": [], "canonical_name": "Wormhole", "type": "interoperability_protocol", "status": "active", "summary": "Wormhole is a cross-chain messaging and asset-transfer protocol. It is included because of the February 2022 exploit involving wrapped ETH on Solana and a widely reported loss of more than $300 million, followed by rapid backfilling of the bridge deficit.", "confidence": "high", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-15", "last_verified_at": "2026-06-15", "aliases": [ "Wormhole Bridge", "Wormhole Token Bridge" ], "launch_date": null, "launch_date_precision": "unknown", "end_date": null, "end_date_precision": "unknown", "terminal_reason": null, "official_url": "https://wormhole.com/", "official_domain": "wormhole.com", "official_url_status": "live", "archived_url": null, "primary_chains": [ "solana", "ethereum" ], "primary_assets": [ "weth" ], "operator_name": "Wormhole", "operator_type": "protocol ecosystem", "ecosystem_name": "Wormhole", "related_protocols": [ "Solana", "Ethereum" ], "brand_history_notes": null, "major_incident_count": 1, "has_unresolved_incident": false, "has_reimbursement_history": true, "successor_id": null, "predecessor_id": null, "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "Seed record focused on the 2022 Wormhole exploit and bridge deficit backfill.", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/wormhole/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "id": "bir_bridge_000003", "slug": "nomad-bridge", "previous_slugs": [], "redirect_from": [], "canonical_name": "Nomad Bridge", "type": "cross_chain_messaging", "status": "limited", "summary": "Nomad Bridge suffered a message-verification exploit in August 2022 and later relaunched a restricted recovery-oriented bridge flow. New canonical-token deposits remained disabled while affected users could bridge back assets and access pro-rata recovered funds.", "confidence": "high", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-15", "last_verified_at": "2026-06-15", "aliases": [ "Nomad", "Nomad token bridge" ], "launch_date": null, "launch_date_precision": "unknown", "end_date": null, "end_date_precision": "unknown", "terminal_reason": null, "official_url": "https://www.nomad.xyz/", "official_domain": "nomad.xyz", "official_url_status": "live", "archived_url": null, "primary_chains": [ "ethereum", "avalanche", "unknown" ], "primary_assets": [ "eth", "usdc", "usdt", "wbtc" ], "operator_name": "Nomad", "operator_type": "protocol ecosystem", "ecosystem_name": "Nomad", "related_protocols": [], "brand_history_notes": null, "major_incident_count": 1, "has_unresolved_incident": true, "has_reimbursement_history": true, "successor_id": null, "predecessor_id": null, "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "Classified as limited because the official recovery bridge relaunched while unrestricted new deposits remained disabled.", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/nomad-bridge/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "id": "bir_bridge_000004", "slug": "harmony-horizon-bridge", "previous_slugs": [], "redirect_from": [], "canonical_name": "Harmony Horizon Bridge", "type": "asset_bridge", "status": "dead", "summary": "Harmony Horizon Bridge is included because of the June 2022 exploit commonly reported at about $100 million. The incident was later attributed by the FBI to Lazarus Group actors, and the bridge's recovery/reimbursement aftermath remains historically significant.", "confidence": "high", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-15", "last_verified_at": "2026-06-15", "aliases": [ "Horizon Bridge", "Harmony Bridge" ], "launch_date": null, "launch_date_precision": "unknown", "end_date": "2022-06", "end_date_precision": "month", "terminal_reason": "Major exploit followed by unresolved recovery/reimbursement status in this seed record.", "official_url": "https://bridge.harmony.one/", "official_domain": "bridge.harmony.one", "official_url_status": "unknown", "archived_url": null, "primary_chains": [ "harmony", "ethereum", "bnb-chain" ], "primary_assets": [ "eth", "usdc", "usdt", "wbtc", "bnb", "one" ], "operator_name": "Harmony", "operator_type": "protocol ecosystem", "ecosystem_name": "Harmony", "related_protocols": [ "Harmony ONE" ], "brand_history_notes": null, "major_incident_count": 1, "has_unresolved_incident": true, "has_reimbursement_history": true, "successor_id": null, "predecessor_id": null, "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "Seed record focused on the 2022 Horizon Bridge exploit and later attribution/recovery context.", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/harmony-horizon-bridge/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "id": "bir_bridge_000005", "slug": "poly-network", "previous_slugs": [], "redirect_from": [], "canonical_name": "Poly Network", "type": "interoperability_protocol", "status": "active", "summary": "Poly Network is included because of the August 2021 exploit commonly reported at more than $600 million. The case is historically important because most or all of the stolen funds were later returned, making it a distinct recovery-centered bridge incident pattern.", "confidence": "high", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-12", "last_verified_at": "2026-06-12", "aliases": [ "Poly Network Bridge" ], "launch_date": null, "launch_date_precision": "unknown", "end_date": null, "end_date_precision": "unknown", "terminal_reason": null, "official_url": "https://poly.network/", "official_domain": "poly.network", "official_url_status": "live", "archived_url": null, "primary_chains": [ "ethereum", "bnb-chain", "polygon" ], "primary_assets": [ "eth", "usdc", "usdt", "wbtc", "bnb", "matic" ], "operator_name": "Poly Network", "operator_type": "protocol ecosystem", "ecosystem_name": "Poly Network", "related_protocols": [], "brand_history_notes": null, "major_incident_count": 1, "has_unresolved_incident": false, "has_reimbursement_history": false, "successor_id": null, "predecessor_id": null, "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "Seed record focused on the 2021 exploit and fund-return aftermath rather than live protocol safety.", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/poly-network/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "id": "bir_bridge_000006", "slug": "bsc-token-hub", "previous_slugs": [], "redirect_from": [ "bnb-bridge" ], "canonical_name": "BSC Token Hub", "type": "canonical_bridge", "status": "deprecated", "summary": "BSC Token Hub was the native bridge between BNB Beacon Chain and BNB Smart Chain. It is included because of the October 2022 forged-proof exploit that created two million BNB, and because the bridge was later retired as part of BNB Chain Fusion.", "confidence": "high", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-14", "last_verified_at": "2026-06-14", "aliases": [ "BNB Bridge", "BNB Chain Token Hub", "BSC TokenHub" ], "launch_date": null, "launch_date_precision": "unknown", "end_date": "2024-11-19", "end_date_precision": "day", "terminal_reason": "Cross-chain communication between BNB Beacon Chain and BNB Smart Chain was disabled during the Beacon Chain final sunset.", "official_url": "https://www.bnbchain.org/en/bnb-chain-fusion", "official_domain": "bnbchain.org", "official_url_status": "live", "archived_url": null, "primary_chains": [ "bnb-beacon-chain", "bnb-chain" ], "primary_assets": [ "bnb" ], "operator_name": "BNB Chain community", "operator_type": "protocol ecosystem", "ecosystem_name": "BNB Chain", "related_protocols": [ "BNB Beacon Chain", "BNB Smart Chain" ], "brand_history_notes": "The historical native bridge was retired during BNB Chain Fusion; the later BNB Chain Bridge is a separate aggregation interface using external bridge partners.", "major_incident_count": 1, "has_unresolved_incident": true, "has_reimbursement_history": false, "successor_id": null, "predecessor_id": null, "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "Seed record distinguishes the nominal value of two million BNB minted from the smaller amount reported as moved off-chain and unrecovered.", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/bsc-token-hub/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "id": "bir_bridge_000007", "slug": "multichain", "previous_slugs": [ "anyswap" ], "redirect_from": [ "anyswap" ], "canonical_name": "Multichain", "type": "cross_chain_router", "status": "dead", "summary": "Multichain was a cross-chain router and bridge protocol formerly known as Anyswap. It is included because of the July 2023 abnormal MPC-controlled asset outflows of more than $125 million and the subsequent announcement that operations would cease.", "confidence": "high", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-14", "last_verified_at": "2026-06-14", "aliases": [ "Anyswap", "Multichain Router" ], "launch_date": null, "launch_date_precision": "unknown", "end_date": "2023-07-14", "end_date_precision": "day", "terminal_reason": "Operations ceased after loss of operational access and funding, following abnormal asset movements and the detention of key personnel described by the team.", "official_url": "https://multichain.org/", "official_domain": "multichain.org", "official_url_status": "unknown", "archived_url": null, "primary_chains": [ "ethereum", "fantom", "bnb-chain", "polygon", "avalanche", "arbitrum" ], "primary_assets": [ "weth", "wbtc", "usdc", "usdt" ], "operator_name": "Multichain", "operator_type": "protocol ecosystem", "ecosystem_name": "Multichain", "related_protocols": [ "Fantom", "Moonriver", "Dogechain" ], "brand_history_notes": "Originally operated as Anyswap before rebranding to Multichain.", "major_incident_count": 1, "has_unresolved_incident": true, "has_reimbursement_history": false, "successor_id": null, "predecessor_id": null, "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "Seed record treats the cause as unresolved and preserves both external-compromise and insider-control interpretations as competing claims.", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/multichain/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "id": "bir_bridge_000008", "slug": "orbit-bridge", "previous_slugs": [], "redirect_from": [ "orbit-chain-bridge" ], "canonical_name": "Orbit Bridge", "type": "interoperability_protocol", "status": "limited", "summary": "Orbit Bridge is a multi-chain interoperability service developed by Ozys. It is included because the Ethereum vault lost approximately $81.5 million in January 2024, followed by a prolonged recovery plan and partial resumption of non-Ethereum bridge functions.", "confidence": "high", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-14", "last_verified_at": "2026-06-14", "aliases": [ "Orbit Chain Bridge", "Orbit IBC Bridge" ], "launch_date": "2020-10", "launch_date_precision": "month", "end_date": null, "end_date_precision": "unknown", "terminal_reason": null, "official_url": "https://bridge.orbitchain.io/", "official_domain": "bridge.orbitchain.io", "official_url_status": "live", "archived_url": null, "primary_chains": [ "orbit-chain", "ethereum" ], "primary_assets": [ "eth", "wbtc", "usdc", "usdt", "dai" ], "operator_name": "Ozys", "operator_type": "company", "ecosystem_name": "Orbit Chain", "related_protocols": [ "Silicon", "Klaytn", "Kaia", "Polygon Agglayer" ], "brand_history_notes": "After the incident, Orbit Bridge functions and assets were progressively migrated toward the Silicon and Polygon Agglayer architecture.", "major_incident_count": 1, "has_unresolved_incident": true, "has_reimbursement_history": true, "successor_id": null, "predecessor_id": null, "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "Seed record treats the service as limited: some bridge functions resumed, while Ethereum-vault asset recovery and normalization remained incomplete.", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/orbit-bridge/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "id": "bir_bridge_000009", "slug": "qubit-qbridge", "previous_slugs": [], "redirect_from": [ "qbridge", "qubit-bridge", "x-bridge" ], "canonical_name": "QBridge", "type": "asset_bridge", "status": "dead", "summary": "QBridge was Qubit Finance's Ethereum-to-BNB Chain bridge and cross-chain collateral pathway. It is included because a January 2022 deposit-logic flaw allowed unbacked xETH minting and the withdrawal of roughly $80 million in assets from Qubit lending markets.", "confidence": "high", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-14", "last_verified_at": "2026-06-14", "aliases": [ "Qubit Bridge", "X-Bridge", "Qubit X-Collateral Bridge" ], "launch_date": null, "launch_date_precision": "unknown", "end_date": "2022-01-28", "end_date_precision": "day", "terminal_reason": "QBridge functions were disabled after the exploit, and reviewed reopening announcements covered Qubit lending markets rather than the bridge itself.", "official_url": "https://qbt.fi/", "official_domain": "qbt.fi", "official_url_status": "live", "archived_url": null, "primary_chains": [ "ethereum", "bnb-chain" ], "primary_assets": [ "eth", "bnb", "weth", "wbtc", "usdc", "usdt" ], "operator_name": "Team Mound", "operator_type": "company", "ecosystem_name": "Qubit Finance", "related_protocols": [ "Bunny Finance", "PancakeBunny" ], "brand_history_notes": "QBridge was the cross-chain component of Qubit Finance; later Qubit market reopening and DAO governance announcements did not establish that the bridge resumed.", "major_incident_count": 1, "has_unresolved_incident": true, "has_reimbursement_history": true, "successor_id": null, "predecessor_id": null, "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "Seed record distinguishes the bridge's terminal status from the partial reopening of Qubit lending markets and ongoing compensation mechanisms.", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/qubit-qbridge/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "id": "bir_bridge_000010", "slug": "thorchain", "previous_slugs": [], "redirect_from": [ "thorchain-bridge" ], "canonical_name": "THORChain", "type": "interoperability_protocol", "status": "paused", "summary": "THORChain is a cross-chain liquidity network and native-asset exchange protocol. It is included because two ETH Router exploits in July 2021 caused a combined protocol insolvency of about $16 million, and a separate May 2026 GG20 TSS exploit drained approximately $10.7 million from an Asgard vault. Normal trading remained temporarily paused at the latest review.", "confidence": "high", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-15", "last_verified_at": "2026-06-15", "aliases": [ "THORChain Network", "THORChain DEX" ], "launch_date": null, "launch_date_precision": "unknown", "end_date": null, "end_date_precision": "unknown", "terminal_reason": null, "official_url": "https://thorchain.org/", "official_domain": "thorchain.org", "official_url_status": "live", "archived_url": null, "primary_chains": [ "thorchain", "bitcoin", "ethereum", "bnb-chain", "avalanche", "unknown" ], "primary_assets": [ "btc", "eth", "usdc", "usdt", "wbtc", "dai", "unknown" ], "operator_name": "THORChain node operators and contributors", "operator_type": "protocol ecosystem", "ecosystem_name": "THORChain", "related_protocols": [ "THORSwap", "Rujira" ], "brand_history_notes": null, "major_incident_count": 3, "has_unresolved_incident": true, "has_reimbursement_history": true, "successor_id": null, "predecessor_id": null, "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "The 2021 router losses were covered through treasury-led recovery and the network later reopened. The May 2026 vault loss remains under investigation and governance-led recovery review. The official site and June 11 restart update still described trading as temporarily paused at verification time.", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/thorchain/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "id": "bir_bridge_000011", "slug": "meter-passport", "previous_slugs": [], "redirect_from": [ "meter-bridge" ], "canonical_name": "Meter Passport", "type": "cross_chain_messaging", "status": "active", "summary": "Meter Passport is Meter Network's cross-chain messaging and asset-transfer bridge. It is included because a February 2022 false-deposit vulnerability enabled unbacked BNB and WETH minting, caused approximately $4.25 million in direct losses, and led to a compensation program before the bridge was rebuilt and restored.", "confidence": "high", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-15", "last_verified_at": "2026-06-15", "aliases": [ "Meter Bridge", "Passport" ], "launch_date": null, "launch_date_precision": "unknown", "end_date": null, "end_date_precision": "unknown", "terminal_reason": null, "official_url": "https://passport.meter.io/", "official_domain": "passport.meter.io", "official_url_status": "live", "archived_url": null, "primary_chains": [ "meter", "ethereum", "bnb-chain", "unknown" ], "primary_assets": [ "bnb", "weth", "unknown" ], "operator_name": "Meter Foundation", "operator_type": "protocol ecosystem", "ecosystem_name": "Meter Network", "related_protocols": [ "VoltSwap", "Hundred Finance" ], "brand_history_notes": "The exploited implementation was later replaced by audited Meter Passport versions based on newer ChainBridge contracts.", "major_incident_count": 1, "has_unresolved_incident": true, "has_reimbursement_history": true, "successor_id": null, "predecessor_id": null, "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "Current documentation describes Meter Passport V2.0. The long-term completion of the PASS-token compensation liability remains a separate historical question.", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/meter-passport/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "id": "bir_bridge_000012", "slug": "allbridge-core", "previous_slugs": [], "redirect_from": [ "allbridge" ], "canonical_name": "Allbridge Core", "type": "asset_bridge", "status": "active", "summary": "Allbridge Core is a native stablecoin bridge connecting EVM and non-EVM networks. It is included because its BNB Chain liquidity pools were exploited in April 2023 through pool-price manipulation, followed by substantial fund recovery, user compensation, contract changes, and relaunch.", "confidence": "high", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-15", "last_verified_at": "2026-06-15", "aliases": [ "Allbridge", "Allbridge Core Bridge" ], "launch_date": null, "launch_date_precision": "unknown", "end_date": null, "end_date_precision": "unknown", "terminal_reason": null, "official_url": "https://allbridge.io/", "official_domain": "allbridge.io", "official_url_status": "live", "archived_url": null, "primary_chains": [ "bnb-chain", "ethereum", "solana", "unknown" ], "primary_assets": [ "usdc", "usdt", "busd" ], "operator_name": "Allbridge", "operator_type": "protocol ecosystem", "ecosystem_name": "Allbridge", "related_protocols": [ "Allbridge Classic" ], "brand_history_notes": "Allbridge Classic is a separate deprecated product line; the active current bridge is Allbridge Core.", "major_incident_count": 1, "has_unresolved_incident": false, "has_reimbursement_history": true, "successor_id": null, "predecessor_id": null, "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "The April 2023 incident affected the previous Allbridge Core liquidity-pool design. The contracts and pool logic were later redeployed and relaunched.", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/allbridge-core/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "id": "bir_bridge_000013", "slug": "li-fi", "previous_slugs": [ "li-finance" ], "redirect_from": [ "lifi", "li-finance" ], "canonical_name": "LI.FI", "type": "bridge_aggregator", "status": "active", "summary": "LI.FI is a cross-chain liquidity aggregation and orchestration protocol that routes through bridges and exchanges. It is included because approval-related smart-contract vulnerabilities caused user-wallet losses in March 2022 and July 2024, while the protocol later resumed and continued expanding.", "confidence": "high", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-15", "last_verified_at": "2026-06-15", "aliases": [ "Li Finance", "LI.FI Protocol" ], "launch_date": null, "launch_date_precision": "unknown", "end_date": null, "end_date_precision": "unknown", "terminal_reason": null, "official_url": "https://li.fi/", "official_domain": "li.fi", "official_url_status": "live", "archived_url": null, "primary_chains": [ "ethereum", "arbitrum", "optimism", "polygon", "solana", "unknown" ], "primary_assets": [ "usdc", "usdt", "dai", "weth", "unknown" ], "operator_name": "LI.FI", "operator_type": "company", "ecosystem_name": "LI.FI", "related_protocols": [ "Jumper", "LI.FI Composer" ], "brand_history_notes": "Previously described publicly as Li Finance before adopting the LI.FI brand.", "major_incident_count": 2, "has_unresolved_incident": true, "has_reimbursement_history": true, "successor_id": null, "predecessor_id": null, "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "The protocol remained active and reported major product and integration growth in 2026. Recovery and reimbursement claims are retained separately for each incident.", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/li-fi/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "id": "bir_bridge_000014", "slug": "chainswap", "previous_slugs": [], "redirect_from": [ "chain-swap" ], "canonical_name": "ChainSwap", "type": "asset_bridge", "status": "active", "summary": "ChainSwap is a permissionless cross-chain asset bridge and aggregation protocol. It is included because two separate July 2021 exploits caused approximately $800,000 and $4 million in reported losses, followed by compensation programs and an August 2021 relaunch.", "confidence": "high", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-15", "last_verified_at": "2026-06-15", "aliases": [ "Chain Swap" ], "launch_date": null, "launch_date_precision": "unknown", "end_date": null, "end_date_precision": "unknown", "terminal_reason": null, "official_url": "https://www.chainswap.com/", "official_domain": "chainswap.com", "official_url_status": "live", "archived_url": null, "primary_chains": [ "ethereum", "bnb-chain", "polygon", "unknown" ], "primary_assets": [ "unknown" ], "operator_name": "ChainSwap", "operator_type": "protocol ecosystem", "ecosystem_name": "ChainSwap", "related_protocols": [ "ChainSwap Cross-chain Aggregator" ], "brand_history_notes": "The 2021 incident records used the ASAP governance-token era of ChainSwap; the current site uses the ChainSwap and CSWAP branding.", "major_incident_count": 2, "has_unresolved_incident": true, "has_reimbursement_history": true, "successor_id": null, "predecessor_id": null, "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "The bridge relaunched after the July 2021 incidents. Final completion of every compensation obligation remains unverified in this reviewed batch.", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/chainswap/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "id": "bir_bridge_000015", "slug": "celer-cbridge", "previous_slugs": [], "redirect_from": [ "cbridge" ], "canonical_name": "Celer cBridge", "type": "asset_bridge", "status": "active", "summary": "Celer cBridge is a non-custodial cross-chain asset bridge operated within the Celer Network ecosystem. It is included because an August 2022 DNS cache-poisoning incident redirected some frontend users to malicious contracts, causing approximately $240,000 in reported losses before the frontend was restored.", "confidence": "high", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-15", "last_verified_at": "2026-06-15", "aliases": [ "cBridge", "Celer Bridge" ], "launch_date": null, "launch_date_precision": "unknown", "end_date": null, "end_date_precision": "unknown", "terminal_reason": null, "official_url": "https://cbridge.celer.network/", "official_domain": "cbridge.celer.network", "official_url_status": "live", "archived_url": null, "primary_chains": [ "ethereum", "bnb-chain", "polygon", "arbitrum", "optimism", "avalanche", "fantom", "unknown" ], "primary_assets": [ "usdc", "usdt", "dai", "weth", "wbtc", "unknown" ], "operator_name": "Celer Network", "operator_type": "protocol ecosystem", "ecosystem_name": "Celer Network", "related_protocols": [ "Celer Inter-chain Message", "State Guardian Network" ], "brand_history_notes": null, "major_incident_count": 1, "has_unresolved_incident": true, "has_reimbursement_history": true, "successor_id": null, "predecessor_id": null, "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "The 2022 incident affected the frontend and DNS path rather than establishing a compromise of the underlying bridge contracts.", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/celer-cbridge/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "id": "bir_bridge_000016", "slug": "socket-protocol", "previous_slugs": [], "redirect_from": [ "socket", "bungee", "socket-gateway" ], "canonical_name": "SOCKET Protocol", "type": "bridge_aggregator", "status": "active", "summary": "SOCKET Protocol provides cross-chain routing and interoperability infrastructure, including the Bungee interface and Socket Gateway contracts. It is included because a January 2024 approval-related exploit caused approximately $3.3 million in reported losses, followed by rapid restoration and recovery of 1,032 ETH.", "confidence": "high", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-15", "last_verified_at": "2026-06-15", "aliases": [ "Socket", "Bungee", "Socket Gateway", "Bungee Bridge" ], "launch_date": null, "launch_date_precision": "unknown", "end_date": null, "end_date_precision": "unknown", "terminal_reason": null, "official_url": "https://www.socket.tech/", "official_domain": "socket.tech", "official_url_status": "live", "archived_url": null, "primary_chains": [ "ethereum", "bnb-chain", "polygon", "arbitrum", "optimism", "avalanche", "unknown" ], "primary_assets": [ "usdc", "usdt", "dai", "weth", "unknown" ], "operator_name": "SOCKET Protocol", "operator_type": "protocol ecosystem", "ecosystem_name": "SOCKET", "related_protocols": [ "Bungee", "Socket Gateway" ], "brand_history_notes": "Bungee is treated as a product/interface of the SOCKET ecosystem in this batch rather than as a separate canonical bridge entity.", "major_incident_count": 1, "has_unresolved_incident": true, "has_reimbursement_history": true, "successor_id": null, "predecessor_id": null, "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "The recovered 1,032 ETH is recorded separately from the reported $3.3 million incident amount. Final distribution completion requires later review.", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/socket-protocol/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "id": "bir_bridge_000017", "slug": "pnetwork", "previous_slugs": [], "redirect_from": [ "ptokens", "pnetwork-ptokens" ], "canonical_name": "pNetwork", "type": "wrapped_asset_bridge", "status": "deprecated", "summary": "pNetwork operated pTokens wrapped-asset bridges and later a broader cross-chain routing protocol. It is included because the pBTC-on-BSC bridge lost 277 BTC in September 2021, the pGALA bridge required an emergency whitehat response in November 2022, and the official pTokens application now states that pNetwork v2 has reached end of life.", "confidence": "high", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-15", "last_verified_at": "2026-06-15", "aliases": [ "pTokens", "pTokens Bridge", "pNetwork / pTokens" ], "launch_date": "2020-03", "launch_date_precision": "month", "end_date": null, "end_date_precision": "unknown", "terminal_reason": "operator_shutdown", "official_url": "https://dapp.p.network/", "official_domain": "p.network", "official_url_status": "live", "archived_url": null, "primary_chains": [ "bitcoin", "ethereum", "bnb-chain", "unknown" ], "primary_assets": [ "btc", "gala", "unknown" ], "operator_name": "pNetwork", "operator_type": "protocol ecosystem", "ecosystem_name": "pNetwork", "related_protocols": [ "pTokens", "pNetwork v2", "Postman" ], "brand_history_notes": "pNetwork v1 launched in March 2020 as the pTokens bridge. pNetwork v2 expanded the system into cross-chain routing and messaging. The official application now labels v2 end-of-life and allows redemption only with explicit risk and timing warnings.", "major_incident_count": 2, "has_unresolved_incident": true, "has_reimbursement_history": true, "successor_id": null, "predecessor_id": null, "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "The DAO interfaces may remain available, but the bridge application itself states that pNetwork v2 has reached end of life. Final completion of the pBTC compensation process and pGALA redistribution remains unverified.", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/pnetwork/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "id": "bir_bridge_000018", "slug": "rainbow-bridge", "previous_slugs": [], "redirect_from": [ "near-rainbow-bridge", "ethereum-bridge-near" ], "canonical_name": "Rainbow Bridge", "type": "canonical_bridge", "status": "active", "summary": "Rainbow Bridge is the trustless, permissionless canonical bridge connecting Ethereum, NEAR, and Aurora. It is included because fabricated-block attacks in May and August 2022 were challenged before user funds were lost, and because official disclosures document additional critical vulnerabilities, a security pause during Ethereum's Merge, and subsequent reactivation.", "confidence": "high", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-15", "last_verified_at": "2026-06-15", "aliases": [ "NEAR Rainbow Bridge", "RainbowBridge" ], "launch_date": "2021-03-15", "launch_date_precision": "day", "end_date": null, "end_date_precision": "unknown", "terminal_reason": null, "official_url": "https://rainbowbridge.app/", "official_domain": "rainbowbridge.app", "official_url_status": "live", "archived_url": null, "primary_chains": [ "ethereum", "near", "aurora" ], "primary_assets": [ "eth", "usdc", "usdt", "dai", "wbtc", "unknown" ], "operator_name": "Aurora Labs", "operator_type": "protocol ecosystem", "ecosystem_name": "NEAR / Aurora", "related_protocols": [ "NEAR Protocol", "Aurora" ], "brand_history_notes": "Rainbow Bridge 2.0 unified earlier Ethereum-to-NEAR and Aurora bridge interfaces under rainbowbridge.app.", "major_incident_count": 2, "has_unresolved_incident": false, "has_reimbursement_history": false, "successor_id": null, "predecessor_id": null, "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "The two canonical incidents are thwarted fabricated-block attacks. Attacker bond losses are not recorded as bridge or user losses. Privately disclosed vulnerabilities are modeled as security events rather than exploited incidents.", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/rainbow-bridge/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "id": "bir_bridge_000019", "slug": "synapse-protocol", "previous_slugs": [], "redirect_from": [ "synapse-bridge" ], "canonical_name": "Synapse Protocol", "type": "interoperability_protocol", "status": "active", "summary": "Synapse Protocol provides cross-chain bridging, liquidity, and messaging infrastructure. It is included because a November 2021 bug in the nUSD metapool implementation allowed price manipulation and an attempted extraction of approximately $8.2 million in nUSD, but validators remained offline and did not process the malicious bridge transaction, allowing affected liquidity providers to be made whole.", "confidence": "high", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-15", "last_verified_at": "2026-06-15", "aliases": [ "Synapse Bridge" ], "launch_date": "2021-08-29", "launch_date_precision": "day", "end_date": null, "end_date_precision": "unknown", "terminal_reason": null, "official_url": "https://bridge.synapseprotocol.com/", "official_domain": "synapseprotocol.com", "official_url_status": "live", "archived_url": null, "primary_chains": [ "ethereum", "avalanche", "bnb-chain", "polygon", "arbitrum", "optimism", "fantom", "unknown" ], "primary_assets": [ "nusd", "usdc", "usdt", "dai", "eth", "unknown" ], "operator_name": "Synapse Protocol", "operator_type": "protocol ecosystem", "ecosystem_name": "Synapse", "related_protocols": [ "Synapse Bridge", "Synapse Messaging" ], "brand_history_notes": "Synapse was introduced as an expansion of the earlier Nerve project. This record does not merge the later, separately operated Nerve Bridge incident into Synapse.", "major_incident_count": 1, "has_unresolved_incident": true, "has_reimbursement_history": true, "successor_id": null, "predecessor_id": null, "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "The official postmortem states that no funds were ultimately lost and that affected Avalanche nUSD liquidity providers would be made whole. Final distribution completion is not independently established in this batch.", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/synapse-protocol/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "id": "bir_bridge_000020", "slug": "nerve-network", "previous_slugs": [], "redirect_from": [ "nerve-bridge", "nervenetwork" ], "canonical_name": "NerveNetwork", "type": "interoperability_protocol", "status": "active", "summary": "NerveNetwork is a heterogeneous-chain interoperability network whose Nerve Bridge and swap-pool infrastructure connects assets across multiple chains. It is included because a November 2021 metapool exploit drained the fUSDT and UST pool liquidity on BNB Chain and yielded approximately 900 BNB to the attacker.", "confidence": "medium", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-16", "last_verified_at": "2026-06-16", "aliases": [ "Nerve Bridge", "NERVE", "NerveNetwork Bridge" ], "launch_date": null, "launch_date_precision": "unknown", "end_date": null, "end_date_precision": "unknown", "terminal_reason": null, "official_url": "https://nerve.network/", "official_domain": "nerve.network", "official_url_status": "live", "archived_url": null, "primary_chains": [ "nerve-network", "bnb-chain", "ethereum", "unknown" ], "primary_assets": [ "fusdt", "ust", "bnb", "unknown" ], "operator_name": "NerveNetwork", "operator_type": "protocol ecosystem", "ecosystem_name": "NerveNetwork", "related_protocols": [ "Nerve Bridge", "NerveSwap", "NULS" ], "brand_history_notes": "The canonical entity is NerveNetwork; Nerve Bridge is treated as its bridge application. It remains separate from Synapse Protocol despite historical naming overlap and shared vulnerable metapool code lineage.", "major_incident_count": 1, "has_unresolved_incident": true, "has_reimbursement_history": false, "successor_id": null, "predecessor_id": null, "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "No stable official postmortem or final reimbursement statement was located for the November 2021 event. Root-cause and amount claims therefore rely primarily on independent security analysis.", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/nerve-network/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "id": "bir_bridge_000021", "slug": "holograph-protocol", "previous_slugs": [], "redirect_from": [ "holograph", "holograph-omnichain" ], "canonical_name": "Holograph Protocol", "type": "interoperability_protocol", "status": "inactive", "summary": "Holograph Protocol operated as an omnichain tokenization protocol intended to preserve token identity across EVM chains. It is included because an attacker abused the Holograph Operator contract in June 2024 to mint one billion unauthorized HLG tokens, prompting a protocol lock, exchange-account freezes, a burn plan, and an investigation involving Halborn and law enforcement.", "confidence": "medium", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-16", "last_verified_at": "2026-06-16", "aliases": [ "Holograph", "Holograph Omnichain Protocol" ], "launch_date": null, "launch_date_precision": "unknown", "end_date": null, "end_date_precision": "unknown", "terminal_reason": null, "official_url": "https://www.holograph.xyz/", "official_domain": "holograph.xyz", "official_url_status": "live", "archived_url": "https://web.archive.org/web/*/https://www.holograph.xyz/", "primary_chains": [ "ethereum", "mantle", "unknown" ], "primary_assets": [ "hlg", "unknown" ], "operator_name": "Holograph", "operator_type": "protocol ecosystem", "ecosystem_name": "Holograph", "related_protocols": [ "Holograph Operator", "Holograph Protocol v1" ], "brand_history_notes": "In 2024 the domain described an omnichain tokenization protocol. At the 2026 review, the same domain described an onchain creator-coin trading terminal and no longer documented the historical cross-chain protocol. This record therefore treats the historical interoperability product as inactive without asserting a legally or technically continuous successor relationship.", "major_incident_count": 1, "has_unresolved_incident": true, "has_reimbursement_history": false, "successor_id": null, "predecessor_id": null, "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "The one-billion-HLG unauthorized mint is not automatically treated as a one-billion-token realized loss. Minted, sold, frozen, and burned quantities remain distinct, and completion of the announced burn plan is unresolved.", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/holograph-protocol/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "id": "bir_bridge_000022", "slug": "ibc-protocol", "previous_slugs": [], "redirect_from": [ "inter-blockchain-communication", "ibc-go", "cosmos-ibc" ], "canonical_name": "Inter-Blockchain Communication Protocol", "type": "cross_chain_messaging", "status": "active", "summary": "The Inter-Blockchain Communication Protocol (IBC) is an open-source, permissionless interoperability protocol for transferring tokens, messages, and arbitrary application data between sovereign blockchains. It is included because the Dragonberry and Huckleberry disclosures required coordinated security responses across IBC-connected infrastructure, while official accounts report no exploitation or user-fund loss from those vulnerabilities.", "confidence": "high", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-16", "last_verified_at": "2026-06-16", "aliases": [ "IBC", "IBC Protocol", "ibc-go", "Cosmos IBC" ], "launch_date": "2021-03-29", "launch_date_precision": "day", "end_date": null, "end_date_precision": "unknown", "terminal_reason": null, "official_url": "https://ibcprotocol.dev/", "official_domain": "ibcprotocol.dev", "official_url_status": "live", "archived_url": null, "primary_chains": [ "cosmos-interchain", "unknown" ], "primary_assets": [ "unknown" ], "operator_name": "IBC open-source community", "operator_type": "open-source protocol community", "ecosystem_name": "Interchain", "related_protocols": [ "ibc-go", "ICS-20", "ICS-23", "IBC Classic", "IBC v2" ], "brand_history_notes": "IBC Classic was first deployed in March 2021. ibc-go is the principal Go implementation and is modeled as implementation context under the protocol entity rather than as a separate bridge entity.", "major_incident_count": 0, "has_unresolved_incident": false, "has_reimbursement_history": false, "successor_id": null, "predecessor_id": null, "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "Dragonberry and Huckleberry are modeled as security-response events rather than exploit incidents because official sources describe vulnerability discovery, coordinated patching, and no known loss.", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/ibc-protocol/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "previous_slugs": [], "redirect_from": [], "confidence": "high", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-18", "last_verified_at": "2026-06-18", "aliases": [ "Ren", "RenVM", "RenBridge", "Ren 1.0" ], "launch_date": "2020-05-27", "launch_date_precision": "day", "end_date": "2022-12", "end_date_precision": "month", "terminal_reason": "Ren 1.0 entered a planned sunset after Alameda-related funding ended; the reviewed current site still describes Ren 2.0 as coming soon.", "archived_url": "https://web.archive.org/web/*/https://renproject.io/", "primary_chains": [ "bitcoin", "ethereum", "bnb-chain", "polygon", "avalanche", "solana", "unknown" ], "primary_assets": [ "renbtc", "btc", "unknown" ], "operator_name": "Ren Foundation and Ren community", "operator_type": "protocol ecosystem", "ecosystem_name": "Ren", "related_protocols": [ "RenVM", "RenBridge", "Ren 1.0", "Ren 2.0" ], "brand_history_notes": "RenVM was the MPC network and RenBridge was an application using it. They remain context under the Ren Protocol entity rather than separate canonical bridge entities.", "major_incident_count": 0, "has_unresolved_incident": false, "has_reimbursement_history": false, "successor_id": null, "predecessor_id": null, "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "No incident record is created for the 2022 sunset. Ren 2.0 is not linked as a successor because reviewed evidence does not establish a public mainnet launch.", "id": "bir_bridge_000023", "slug": "ren-protocol", "canonical_name": "Ren Protocol", "type": "interoperability_protocol", "status": "deprecated", "summary": "Ren Protocol operated RenVM and RenBridge as cross-chain infrastructure for native assets including Bitcoin. The reviewed Ren 1.0 lineage ended after Alameda-related funding stopped in late 2022, while Ren 2.0 remained announced but not verified as a public mainnet successor.", "official_url": "https://renprotocol.org/", "official_domain": "renprotocol.org", "official_url_status": "live", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/ren-protocol/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "previous_slugs": [], "redirect_from": [], "confidence": "high", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-18", "last_verified_at": "2026-06-18", "aliases": [ "AEB", "Avalanche Ethereum Bridge" ], "launch_date": "2021-02-08", "launch_date_precision": "day", "end_date": "2021-07-29", "end_date_precision": "day", "terminal_reason": "Officially replaced by Avalanche Bridge on July 29, 2021; AEB transfers were subsequently disabled and legacy assets moved to an upgrade path.", "archived_url": "https://web.archive.org/web/*/https://aeb.xyz/", "primary_chains": [ "ethereum", "avalanche" ], "primary_assets": [ "weth", "usdc", "usdt", "dai", "wbtc" ], "operator_name": "Ava Labs and AEB relayers", "operator_type": "protocol ecosystem", "ecosystem_name": "Avalanche", "related_protocols": [ "ChainBridge", "Avalanche Bridge" ], "brand_history_notes": "AEB used the earlier ChainBridge-style relayer architecture. The successor Avalanche Bridge is a separate canonical entity.", "major_incident_count": 0, "has_unresolved_incident": false, "has_reimbursement_history": false, "successor_id": "bir_bridge_000025", "predecessor_id": null, "replacement_bridge_id": "bir_bridge_000025", "duplicate_of": null, "merged_into": null, "notes": "Residual support for upgrading deprecated AEB assets is legacy support and does not make AEB active.", "id": "bir_bridge_000024", "slug": "avalanche-ethereum-bridge", "canonical_name": "Avalanche-Ethereum Bridge", "type": "canonical_bridge", "status": "migrated", "summary": "The Avalanche-Ethereum Bridge was Avalanche's first official Ethereum bridge. It launched in February 2021 and was replaced in July 2021 by the SGX-based Avalanche Bridge, followed by relayer shutdown and migration of bridged assets.", "official_url": "https://aeb.xyz/", "official_domain": "aeb.xyz", "official_url_status": "dead", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/avalanche-ethereum-bridge/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "previous_slugs": [], "redirect_from": [], "confidence": "high", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-18", "last_verified_at": "2026-06-18", "aliases": [ "AB", "Avalanche EVM Bridge", "Avalanche Core Bridge" ], "launch_date": "2021-07-29", "launch_date_precision": "day", "end_date": null, "end_date_precision": "unknown", "terminal_reason": null, "archived_url": null, "primary_chains": [ "ethereum", "avalanche" ], "primary_assets": [ "weth", "usdc", "usdt", "dai", "wbtc" ], "operator_name": "Ava Labs and Bridge Node operators", "operator_type": "protocol ecosystem", "ecosystem_name": "Avalanche", "related_protocols": [ "Core", "Avalanche Bridge Nodes" ], "brand_history_notes": "Launched as the next-generation replacement for AEB with a distinct SGX and Bridge Node architecture.", "major_incident_count": 0, "has_unresolved_incident": false, "has_reimbursement_history": false, "successor_id": null, "predecessor_id": "bir_bridge_000024", "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "Batch 5 establishes the predecessor relationship and current active status; it does not claim to provide a complete incident history for the current bridge.", "id": "bir_bridge_000025", "slug": "avalanche-bridge", "canonical_name": "Avalanche Bridge", "type": "canonical_bridge", "status": "active", "summary": "Avalanche Bridge is the SGX and Bridge Node based official bridge connecting Ethereum and Avalanche C-Chain. It launched on July 29, 2021 as the explicit replacement for the Avalanche-Ethereum Bridge and remains supported through Core.", "official_url": "https://core.app/bridge/", "official_domain": "core.app", "official_url_status": "live", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/avalanche-bridge/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" }, { "previous_slugs": [], "redirect_from": [], "confidence": "high", "record_maturity": "reviewed", "update_status": "current", "last_reviewed_at": "2026-06-18", "last_verified_at": "2026-06-18", "aliases": [ "Conflux ShuttleFlow" ], "launch_date": "2020", "launch_date_precision": "year", "end_date": "2024-01-06", "end_date_precision": "day", "terminal_reason": "Bridge operations migrated to Zero Gravity in November 2023, followed by a claim-only period and final ShuttleFlow website and dApp shutdown in January 2024.", "archived_url": "https://web.archive.org/web/*/https://shuttleflow.io/", "primary_chains": [ "conflux-core-space", "conflux-espace", "ethereum", "bnb-chain", "unknown" ], "primary_assets": [ "cfx", "eth", "usdt", "unknown" ], "operator_name": "Conflux Foundation and ecosystem partners", "operator_type": "protocol ecosystem", "ecosystem_name": "Conflux", "related_protocols": [ "Zero Gravity Portal", "KinetFlow" ], "brand_history_notes": "Official closure material described a technology and operational handoff to Zero Gravity. KinetFlow later replaced Zero Gravity Portal using technology from both services.", "major_incident_count": 0, "has_unresolved_incident": false, "has_reimbursement_history": false, "successor_id": null, "predecessor_id": null, "replacement_bridge_id": null, "duplicate_of": null, "merged_into": null, "notes": "No successor_id is set because Zero Gravity is not a reviewed canonical entity in this batch.", "id": "bir_bridge_000026", "slug": "shuttleflow", "canonical_name": "ShuttleFlow", "type": "interoperability_protocol", "status": "migrated", "summary": "ShuttleFlow was Conflux's cross-chain asset protocol and multi-chain bridge. Bridge operations ended in November 2023 with technology and service migration to Zero Gravity, while a limited claim path remained until the website and dApp closed in January 2024.", "official_url": "https://shuttleflow.io/", "official_domain": "shuttleflow.io", "official_url_status": "dead", "canonical_page_url": "https://bridge-incident-registry.pages.dev/bridge/shuttleflow/", "canonical_data_url": "https://bridge-incident-registry.pages.dev/data/bridges.json" } ]