{
"daLayer": "ethereum",
"name": "Enshrined Bridge",
"risks": {
"daBridge": {
"value": "Enshrined",
"sentiment": "good",
"description": "Rollup users have access to all the data, as it is posted onchain on the consensus layer. On the execution layer, the rollup relies on blob data commitment (versioned hashes), which are accessible through the BLOBHASH opcode. \nThe rollup smart contracts can use these blob commitments during state transition validation to reference blobs during proof verification, without requiring direct access to the raw blob data.\n "
},
"callout": "Unlike non-enshrined DA bridges, it does not place any honesty\nassumption on an external committee that provides data availability\nattestations to the DA bridge. From the rollup perspective,\nEthereum's canonical chain cannot contain unavailable data\ncommitments as full nodes self-verify the data availability of each\nblock, discarding blocks with unavailable data. The rollup state\nvalidating bridge has access to all the data, as it is posted on chain."
},
"technology": {
"description": "## Enshrined Bridge\nThe DA bridge on Ethereum is enshrined, meaning that blob data is directly accessible on the consensus layer, with data availability guaranteed by the network's inherent consensus rules. \nIf a block contains unavailable data, full nodes will reject it, causing the chain to fork away from that block. This ensures data availability without requiring additional trust assumptions. \nIn contrast, external DA providers must rely on data availability attestations from the external validator set, introducing an extra layer of trust on the majority of validators."
},
"usedIn": [
{
"id": "abstract",
"name": "Abstract",
"slug": "abstract"
},
{
"id": "adi",
"name": "ADI Chain",
"slug": "adi"
},
{
"id": "arbitrum",
"name": "Arbitrum One",
"slug": "arbitrum"
},
{
"id": "aztecnetwork",
"name": "Aztec Network",
"slug": "aztecnetwork"
},
{
"id": "base",
"name": "Base Chain",
"slug": "base"
},
{
"id": "blast",
"name": "Blast",
"slug": "blast"
},
{
"id": "bob",
"name": "BOB",
"slug": "bob"
},
{
"id": "bobanetwork",
"name": "Boba Network",
"slug": "bobanetwork"
},
{
"id": "cartesi-prt-honeypot-v2",
"name": "Cartesi PRT Honeypot v2",
"slug": "cartesi-prt-honeypot-v2"
},
{
"id": "dbk",
"name": "DeBank Chain",
"slug": "dbk"
},
{
"id": "deri",
"name": "Deri",
"slug": "deri"
},
{
"id": "ethscriptions",
"name": "Ethscriptions",
"slug": "ethscriptions"
},
{
"id": "facet",
"name": "Facet",
"slug": "facet"
},
{
"id": "fluent",
"name": "Fluent",
"slug": "fluent"
},
{
"id": "forknet",
"name": "Forknet",
"slug": "forknet"
},
{
"id": "hashkey",
"name": "HashKey Chain",
"slug": "hashkey"
},
{
"id": "hemi",
"name": "Hemi",
"slug": "hemi"
},
{
"id": "ink",
"name": "Ink",
"slug": "ink"
},
{
"id": "katana",
"name": "Katana",
"slug": "katana"
},
{
"id": "lighter",
"name": "Lighter",
"slug": "lighter"
},
{
"id": "linea",
"name": "Linea",
"slug": "linea"
},
{
"id": "lisk",
"name": "Lisk",
"slug": "lisk"
},
{
"id": "loopring",
"name": "Loopring",
"slug": "loopring"
},
{
"id": "mantle",
"name": "Mantle",
"slug": "mantle"
},
{
"id": "metal",
"name": "Metal",
"slug": "metal"
},
{
"id": "metis",
"name": "Metis Andromeda",
"slug": "metis"
},
{
"id": "mode",
"name": "Mode Network",
"slug": "mode"
},
{
"id": "morph",
"name": "Morph",
"slug": "morph"
},
{
"id": "optimism",
"name": "OP Mainnet",
"slug": "op-mainnet"
},
{
"id": "phala",
"name": "Phala",
"slug": "phala"
},
{
"id": "r0ar",
"name": "R0ar",
"slug": "r0ar"
},
{
"id": "race",
"name": "Race Network",
"slug": "race"
},
{
"id": "scroll",
"name": "Scroll",
"slug": "scroll"
},
{
"id": "shape",
"name": "Shape",
"slug": "shape"
},
{
"id": "soneium",
"name": "Soneium",
"slug": "soneium"
},
{
"id": "starknet",
"name": "Starknet",
"slug": "starknet"
},
{
"id": "superseed",
"name": "Superseed",
"slug": "superseed"
},
{
"id": "swan",
"name": "Swan Chain",
"slug": "swan"
},
{
"id": "swell",
"name": "Swellchain",
"slug": "swell"
},
{
"id": "sxnetwork",
"name": "SX Network",
"slug": "sxnetwork"
},
{
"id": "syndicate",
"name": "Syndicate Chain",
"slug": "syndicate"
},
{
"id": "taiko",
"name": "Taiko Alethia",
"slug": "taiko"
},
{
"id": "unichain",
"name": "Unichain",
"slug": "unichain"
},
{
"id": "worldchain",
"name": "World Chain",
"slug": "world"
},
{
"id": "xlayer",
"name": "X Layer",
"slug": "xlayer"
},
{
"id": "zeronetwork",
"name": "ZERO Network",
"slug": "zeronetwork"
},
{
"id": "zircuit",
"name": "Zircuit",
"slug": "zircuit"
},
{
"id": "zksync2",
"name": "ZKsync Era",
"slug": "zksync-era"
},
{
"id": "zora",
"name": "Zora",
"slug": "zora"
}
]
}
loopring+38-157
statuses+2-1
{
"unverifiedContracts": []
"unverifiedContracts": [],
"yellowWarning": "Loopring DEX was [sunset](https://x.com/loopringorg/status/2071253250725322987) and no longer accepts deposits. The Loopring Team plans to send out deposited assets directly to users."
}
milestones+7-0
[
{
"title": "Loopring DEX sunsets",
"url": "https://x.com/loopringorg/status/2071253250725322987",
"date": "2026-06-28T00:00:00Z",
"description": "Loopring announces the DEX sunset, deposited tokens will be transferred to users.",
"type": "general"
},
{
"title": "DeFi Closure Announcement",
"url": "https://medium.com/loopring-protocol/loopring-defi-closure-announcement-e9270cccba4d",
"date": "2025-07-31T00:00:00Z",
"description": "Loopring sunsets DeFi features to focus on the L2.",
"type": "general"
},
{
"title": "Loopring ZK Rollup is live",
"url": "https://medium.com/loopring-protocol/loopring-protocol-3-0-zksnarks-for-scalability-845b35a8b75b",
"date": "2019-12-04T00:00:00Z",
"description": "Loopring Protocol 3.0 is fully operational with support for orderbook trading on WeDex.",
"type": "general"
},
{
"title": "Loopring Protocol 3.6 Pre-release",
"url": "https://medium.loopring.io/loopring-3-6-is-code-complete-and-security-audit-has-begun-68a642506e31",
"date": "2020-09-22T00:00:00Z",
"description": "Enhancements in transfers, order-book trading and AMM swap.",
"type": "general"
},
{
"title": "Loopring’s ZK Rollup AMM is Live",
"url": "https://medium.loopring.io/looprings-zkrollup-amm-is-live-2f8251cd0fcd",
"date": "2020-12-02T00:00:00Z",
"description": "Improved implementation, enabling gas-free instant swaps and liquidity changes.",
"type": "general"
},
{
"title": "Loopring Supports Payments",
"url": "https://medium.loopring.io/loopring-pay-is-live-zkrollup-transfers-on-ethereum-770d35213408",
"date": "2020-06-06T00:00:00Z",
"description": "Support for ERC20 transfers is live on Loopring.",
"type": "general"
},
{
"title": "DeFi Port is Live on Loopring",
"url": "https://medium.loopring.io/loopring-l2-defi-port-cd6e811250a9",
"date": "2022-09-27T00:00:00Z",
"description": "Dutch auctions, lending, and other DeFi functions can be performed on Loopring.",
"type": "general"
},
{
"title": "Loopring Supports NFTs",
"url": "https://medium.loopring.io/loopring-now-supports-nfts-on-l2-29174a343d0d",
"date": "2021-08-24T00:00:00Z",
"description": "Loopring supports NFT minting, trading, and transfers.",
"type": "general"
},
{
"title": "Loopring DEX is online",
"url": "https://medium.loopring.io/loopring-launches-zkrollup-exchange-loopring-io-d6a85beeed21",
"date": "2020-02-27T00:00:00Z",
"description": "ZK Rollup trading is live, as Loopring launches their order book based exchange.",
"type": "general"
}
]
scalingTechnology+1-18
{
"dataAvailability": [
{
"name": "All data required for proofs is published onchain",
"description": "All the data that is used to construct the system state is published onchain in the form of cheap calldata. This ensures that it will always be available when needed.",
"risks": [],
"references": [
{
"title": "Introduction - Loopring design doc",
"url": "https://github.com/Loopring/protocols/blob/master/packages/loopring_v3/DESIGN.md#introduction"
}
]
}
],
"exitMechanisms": [
{
"name": "Regular exit",
"description": "The user initiates the withdrawal by submitting a regular transaction on this chain. When the block containing that transaction is settled the funds become available for withdrawal on L1. ZK proofs are required to settle blocks. Finally the user submits an L1 transaction to claim the funds.",
"risks": [],
"references": [
{
"title": "Withdraw - Loopring design doc",
"url": "https://github.com/Loopring/protocols/blob/master/packages/loopring_v3/DESIGN.md#withdraw"
}
]
},
{
"name": "Forced exit",
"description": "If the user experiences censorship from the operator with regular exit they can submit their withdrawal requests directly on L1. The system is then obliged to service this request. Once the force operation is submitted and if the request is serviced, the operation follows the flow of a regular exit.",
"risks": [],
"references": [
{
"title": "Forced Request Handling - Loopring design doc",
"url": "https://github.com/Loopring/protocols/blob/master/packages/loopring_v3/DESIGN.md#forced-request-handling"
},
{
"title": "ExchangeV3.sol#L8118 - Loopring source code, forceWithdraw function",
"url": "https://etherscan.io/address/0x26d8Ba776a067C5928841985bCe342f75BAE7E82#code#L8118"
}
]
},
{
"name": "Emergency exit",
"description": "If the 15d deadline passes and the forced exit is still ignored the user can put the system into Withdrawal Mode, disallowing further state updates. In that case everybody can withdraw by submitting a merkle proof of their funds with their L1 transaction.",
"risks": [],
"references": [
{
"title": "Forced Request Handling - Loopring design doc",
"url": "https://github.com/Loopring/protocols/blob/master/packages/loopring_v3/DESIGN.md#forced-request-handling"
},
{
"title": "ExchangeV3.sol#L8159 - Loopring source code, withdrawFromMerkleTree function",
"url": "https://etherscan.io/address/0x26d8Ba776a067C5928841985bCe342f75BAE7E82#code#L8159"
}
]
}
],
"forceTransactions": {
"name": "Users can force exit the system",
"description": "Force exit allows the users to escape censorship by withdrawing their funds. The system allows users to force the withdrawal of funds by submitting a request directly to the contract onchain. The request must be served within a defined time period. If this does not happen, the system will halt regular operation and permit trustless withdrawal of funds.",
"risks": [
{
"category": "Users can be censored if",
"text": "the operator refuses to include their transactions. However, there exists a mechanism to independently exit the system."
}
],
"references": [
{
"title": "Forced Withdrawals - Loopring design doc",
"url": "https://github.com/Loopring/protocols/blob/master/packages/loopring_v3/DESIGN.md#forced-withdrawals"
},
{
"title": "Forced Request Handling - Loopring design doc",
"url": "https://github.com/Loopring/protocols/blob/master/packages/loopring_v3/DESIGN.md#forced-request-handling"
}
]
},
"operator": {
"name": "The system has a centralized operator",
"description": "The operator is the only entity that can propose blocks. A live and trustworthy operator is vital to the health of the system.",
"risks": [
{
"category": "MEV can be extracted if",
"text": "the operator exploits their centralized position and frontruns user transactions."
}
],
"references": [
{
"title": "ExchangeV3.sol#L315-L322 - Etherscan source code, submitBlocks function",
"url": "https://etherscan.io/address/0x26d8Ba776a067C5928841985bCe342f75BAE7E82#code#L8022"
},
{
"title": "LoopringIOExchangeOwner.sol#L123-L126 - Etherscan source code, hasAccessTo function call",
"url": "https://etherscan.io/address/0x153CdDD727e407Cb951f728F24bEB9A5FaaA8512#code#L5539"
}
]
"references": []
},
"stateValidation": {
"description": "Each update to the system state must be accompanied by a ZK proof that ensures that the new state was derived by correctly applying a series of valid user transactions to the previous state. These proofs are then verified on Ethereum by a smart contract.",
"categories": [
{
"title": "ZK Circuits",
"description": "Loopring utilizes Groth16 for their proving system. The source code of the circuits can be found [here](https://github.com/Loopring/protocol3-circuits).",
"risks": [
{
"category": "Funds can be lost if",
"text": "the proof system is implemented incorrectly."
}
]
},
{
"title": "Verification Keys Generation",
"description": "Groth16 requires a circuit specific trusted setup, so they run their own ceremony. The first phase is run using Powers of Tau ceremony. Some of the instructions on how to regenerate the verification keys can be found [here](https://github.com/Loopring/trusted_setup/tree/loopring-3.6.2)."
},
{
"title": "Validity proofs",
"description": "Each update to the system state must be accompanied by a ZK proof that ensures that the new state was derived by correctly applying a series of valid user transactions to the previous state. These proofs are then verified on Ethereum by a smart contract.",
"risks": [],
"references": [
{
"title": "Operators - Loopring design doc",
"url": "https://github.com/Loopring/protocols/blob/master/packages/loopring_v3/DESIGN.md#operators"
}
]
}
]
}
}