Search

Search for projects by name

SummaryMilestones & IncidentsRisk summaryRisk analysisRollup stageData availabilityState derivationState validationOperatorWithdrawalsPermissionsSmart contracts

DeGate Legacy logoDeGate Legacy

This project is archived.
This project is in shutdown mode and no longer active.

Badges

About

DeGate is an app-specific ZK Rollup that enables a trustless, fast and low-fee decentralized order book exchange, helping users to trade easy and sleep easy. DeGate smart contracts are forked from Loopring V3.

Value secured
$0.000.00%
Canonically Bridged
$0.00
Natively Minted
$0.00
Externally Bridged
$0.00
  • Tokens
    No data
  • Past day UOPS
    No data
  • 30D ops count
    No data
  • Stage
  • Type
    ZK Rollup
  • Purpose
    Exchange
    • Sequencer failureState validationData availabilityExit windowProposer failure

    Badges

    About

    DeGate is an app-specific ZK Rollup that enables a trustless, fast and low-fee decentralized order book exchange, helping users to trade easy and sleep easy. DeGate smart contracts are forked from Loopring V3.

    Milestones & Incidents

    DeGate DEX Launches Mainnet Beta

    2023 May 3rd

    DeGate launches mainnet beta with a deposit cap and a program to recover eventual user losses.

    Learn more
    Risk summary

    MEV can be extracted if

    1. the operator exploits their centralized position and frontruns user transactions.
    Risk analysis
    Sequencer failureState validationData availabilityExit windowProposer failure
    Sequencer failure
    Force via L1

    Users can force the sequencer to include a withdrawal transaction by submitting a request through L1 with a 0.01 ETH fee. If the sequencer is down for more than 15d, users can use the exit hatch to withdraw their funds. The sequencer can censor individual deposits, but in such case after 15d users can get their funds back.

    State validation
    ZK proofs (SN)

    SNARKs are zero knowledge proofs that ensure state correctness, but require trusted setup.

    Data availability
    Onchain

    All of the data needed for proof construction is published on Ethereum L1.

    Exit window
    ∞

    Users can exit funds at any time because contracts are not upgradeable.

    Proposer failure
    Use escape hatch

    Users are able to trustlessly exit by submitting a Merkle proof of funds.

    Rollup stageDeGate LegacyDeGate Legacy is a
    Stage 2
    Appchain
    ZK Rollup.

    Learn more about Rollup stages
    Please keep in mind that these stages do not reflect rollup security, this is an opinionated assessment of rollup maturity based on subjective criteria, created with a goal of incentivizing projects to push toward better decentralization. Each team may have taken different paths to achieve this goal.
    Data availability

    All data required for proofs is published onchain

    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.

    1. Introduction - DeGate design doc
    Learn more about the DA layer here: Ethereum logoEthereum
    State derivation
    Node software

    Node software source code can be found here.

    Compression scheme

    No compression is used.

    Genesis state

    The system does not begin with a genesis state; instead, it initiates from a zero state, as referenced in CreateEmptyState.

    Data format

    DeGate bundles off-chain transactions into zkBlocks and submits them to the blockchain. zkBlock data definition is documented here.

    State validation
    Validity proofs

    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.

    1. Operator - DeGate design doc
    Operator

    The system has a centralized operator

    The operator is the only entity that can propose blocks. A live and trustworthy operator is vital to the health of the system.

    • MEV can be extracted if the operator exploits their centralized position and frontruns user transactions.

    1. ExchangeV3.sol#L341-L348 - DeGate source code
    2. LoopringIOExchangeOwner.sol#L98-L101 - DeGate source code

    Users can force exit the system

    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.

    • Users can be censored if the operator refuses to include their transactions. However, there exists a mechanism to independently exit the system.

    1. Forced Withdrawals - DeGate design doc
    Withdrawals

    Regular exit

    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.

    1. Withdraw - DeGate design doc

    Forced exit

    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.

    1. Forced Request Handling - DeGate design doc
    2. ExchangeV3.sol#L392 - DeGate source code, forceWithdraw function

    Emergency exit

    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.

    1. Forced Request Handling - DeGate design doc
    2. ExchangeV3.sol#L420 - DeGate source code, withdrawFromMerkleTree function
    Permissions

    Ethereum

    Actors:

    DefaultDepositContract Owner 0x2028…da52

    This address is the owner of the following contracts: LoopringIOExchangeOwner, LoopringV3, DefaultDepositContract. Can add or remove block submitters. Can change the forced withdrawal fee up to 0.25 ETH. Can change a way that balance is calculated per contract during the deposit, allowing the support of non-standard tokens.

    Used in:

    BlockVerifier Owner 0xd8C6…2e0F

    This address is the owner of the BlockVerifier contract.

    Block Submitters (2) 0x84A0…70a00xE9A3…b77C

    Actors who can submit new blocks, updating the L2 state on L1.

    Smart contracts

    Ethereum

    ExchangeV3 0xe636…4eD5

    Main ExchangeV3 contract.

    LoopringIOExchangeOwner 0x6B93…aE83

    Contract used by the Prover to submit exchange blocks with zkSNARK proofs that are later processed and verified by the BlockVerifier contract.

    DefaultDepositContract 0x814d…d1dA

    ERC 20 token basic deposit contract. Handles user deposits and withdrawals. This contract can store any token.

    LoopringV3 0x4d70…c458

    Contract for setting exchange fee parameters.

    BlockVerifier 0x1c60…4C9e

    zkSNARK Verifier based on ethsnarks library.

    Value Secured is calculated based on these smart contracts and tokens:

    Generic escrow 0x814d…d1dA