DeGateSubmit a Bug
DeGate is a decentralized orderbook exchange (DEX) built on the Ethereum blockchain that utilizes zero-knowledge technology. DeGate DEX offers spot market trading with limit orders and also offers a grid trading function. DeGate operates as a decentralized autonomous organization (DAO). The DEX platform is focused on being user-friendly and is built on the principle of Trustlessness, or ‘Can’t do evil’, with no admin key. With DeGate’s unique Efficient Gas Saving technology, users can expect super-low gas fees while using a decentralized protocol. Another critical component of DeGate is the Permissionless Listing feature which enables any token to be listed in a permissionless manner on DeGate’s orderbook DEX.
For more information about DeGate, please visit https://docs.degate.com/.
DeGate Testnet is currently live on https://testnet.degate.com/, and more details can be found in the product documentation (https://docs.degate.com/v/product_en/overview)
The bounty environment has been deployed on Public Testnet, whose code was open sourced on Github, along with the Protocol Specification Docs, Circuit Design Docs and Smart Contract Design Docs.
For Whitehats: It is highly recommended that you review the details of this program in full. Although many Bug Bounty programs have standard terms and conditions, each also has their own unique details that are critical to your success.
Prior to submitting a report please review the Immunefi Bug Report Template and Best Practices.
Rewards by Threat Level
Please review how rewards are distributed based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale system with separate scales for Smart Contracts and Websites/Apps.
Payouts and Payout Requirements:
Payouts are handled by the DeGate team directly and are denominated in USD. However, payouts are done in USDC. DeGate commits to honoring payouts according to the terms set out in this program at the time of report submission, and to treat this program as the agreement and source of truth concerning bug reports and responsible disclosures.
For the purposes of determining report validity, this is a Primacy of Impact program.
Learn more about report validity best practices here: Best Practice - Primacy of Impact vs Primacy of Rules.
DeGate does not have a Know Your Customer (KYC) requirement for bug bounty payouts.
Audit Discoveries and Known Issues:
Bug reports covering previously-discovered bugs are not eligible for any reward through the bug bounty program. If a bug report covers a known issue, it may be rejected together with proof of the issue being known before escalation of the bug report via Immunefi.
- USD $1,110,000
- USD $100,000
- USD $5,000
- USD $1,500
Websites and Applications
- USD $100,000
- USD $5,000
- USD $2,500
- USD $1,000
Below are a list of audits completed for DeGate. All bugs reported in these audits are considered as out-of-scope for the bug bounty program.
- https://github.com/degatedev/protocols/blob/degate_mainnet/packages/loopring_v3/security_audit/Least%20Authority%20-%20DeGate%20DAO%20DeGate%20Smart%20Contracts%20Updated%20Final%20Audit%20Report.pdfLinkLeast Authority (previous code) - 2022-07-04Auditor & Completion
- https://github.com/degatedev/protocols/blob/degate_mainnet/packages/loopring_v3/security_audit/Least%20Authority%20-%20DeGate%20Technology%20DeGate%20zk-SNARK%20Circuit%20Final%20Audit%20Report.pdfLinkLeast Authority (previous code) - 2022-05-06Auditor & Completion
- https://github.com/degatedev/protocols/blob/degate_mainnet/packages/loopring_v3/security_audit/DeGate_Report_EN-final2023.pdfLinkSecbit (latest code) - 2023-03-23Auditor & Completion
Assets in scope
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/contracts/core/iface/ExchangeData.solTargetSmart Contract - Exchange DataType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/contracts/core/iface/IBlockVerifier.solTargetSmart Contract - IBlock VerifierType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/contracts/core/iface/IDepositContract.solTargetSmart Contract - IDeposit ContractType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/contracts/core/iface/IExchangeV3.solTargetSmart Contract - IExchange V3Type
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/contracts/core/iface/ILoopringV3.solTargetSmart Contract - ILoopring V3Type
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/contracts/core/impl/BlockVerifier.solTargetSmart Contract - Block VerifierType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/contracts/core/impl/DefaultDepositContract.solTargetSmart Contract - Default Deposit ContractType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/contracts/core/impl/ExchangeV3.solTargetSmart Contract - Exchange V3Type
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/contracts/core/impl/LoopringV3.solTargetSmart Contract - Loopring V3Type
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/contracts/core/impl/VerificationKeys.solTargetSmart Contract - Verification KeysType
- https://github.com/degatedev/protocols/tree/degate1.0.0/packages/loopring_v3/contracts/core/impl/libexchangeTargetSmart Contract - Lib ExchangeType
- https://github.com/degatedev/protocols/tree/degate1.0.0/packages/loopring_v3/contracts/core/impl/libtransactionsTargetSmart Contract - Lib TransactionsType
- Smart Contract - LibType
- Smart Contract - AuxType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/circuit/Circuits/UniversalCircuit.hTargetSmart Contract - Universal CircuitType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/circuit/Circuits/BaseTransactionCircuit.hTargetSmart Contract - Base Transaction CircuitType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/circuit/Circuits/Circuit.hTargetSmart Contract - CircuitType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/circuit/Circuits/NoopCircuit.hTargetSmart Contract - Noop CircuitType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/circuit/Circuits/DepositCircuit.hTargetSmart Contract - Deposit CircuitType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/circuit/Circuits/AccountUpdateCircuit.hTargetSmart Contract - Account Update CircuitType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/circuit/Circuits/AppKeyUpdateCircuit.hTargetSmart Contract - App Key Update CircuitType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/circuit/Circuits/TransferCircuit.hTargetSmart Contract - Transfer CircuitType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/circuit/Circuits/WithdrawCircuit.hTargetSmart Contract - Withdraw CircuitType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/circuit/Circuits/SpotTradeCircuit.hTargetSmart Contract - Spot Trade CircuitType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/circuit/Circuits/OrderCancelCircuit.hTargetSmart Contract - Order Cancel CircuitType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/circuit/Gadgets/AccountGadgets.hTargetSmart Contract - Account GadgetsType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/circuit/Gadgets/BatchOrderGadgets.hTargetSmart Contract - Batch Order GadgetsType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/circuit/Gadgets/MatchingGadgets.hTargetSmart Contract - Matching GadgetsType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/circuit/Gadgets/MathGadgets.hTargetSmart Contract - Math GadgetsType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/circuit/Gadgets/MerkleTree.hTargetSmart Contract - Merkle TreeType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/circuit/Gadgets/OrderGadgets.hTargetSmart Contract - Order GadgetsType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/circuit/Gadgets/SignatureGadgets.hTargetSmart Contract - Signature GadgetsType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/circuit/Gadgets/StorageGadgets.hTargetSmart Contract - Storage GadgetsType
- https://github.com/degatedev/protocols/blob/degate1.0.0/packages/loopring_v3/circuit/Utils/Constants.hTargetSmart Contract - ConstantsType
- TargetSmart Contract - DataType
- TargetSmart Contract - UtilsType
- Websites and Applications - Main WebsiteType
- Websites and Applications - Python SDKType
- Websites and Applications - Go SDKType
- Websites and Applications - Api docsType
- Websites and Applications - BackendType
Impacts only apply to assets in active use by the project like contracts on mainnet or web/app assets used in production. Any impact that applies to assets not in active use, like test or mock files, are out-of-scope of the bug bounty program unless explicitly mentioned as in-scope.
- Smart Contracts - PoC, For Smart contracts and Circuits bug reports, all bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required. Bug reports are required to include a runnable PoC in order to prove impact. Exceptions may be made in cases where the vulnerability is objectively evident from simply mentioning the vulnerability and where it exists. However, the bug reporter may be required to provide a PoC at any point in time.
- For more information on PoCs please visit: Proof of Concept (PoC) Guidelines and Rules
- Web/App - Bug reports are to include a runnable Proof of Concept (PoC) in order to prove impact. All web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. All PoC content must adhere to the PoC guidelines and rules of Immunefi. In the event that a PoC requires an attack on a web/app asset provided, they must still adhere to the rules provided, otherwise eligibility for a reward may be revoked.
- For more information on PoCs please visit: Proof of Concept (PoC) Guidelines and Rules
Whitehats we highly encourage you to review any potential subdomains and what specific port(s) are in scope. Even though the domain may be the same, different ports may point to different assets.
Dev Environment and Documentation:
DeGate has included dev documentation and/or instructions to help in reviewing code and exploring for bugs:
Impacts to other assets
Hackers are encouraged to submit issues outside of the outlined Impacts and Assets in Scope.
If whitehats can demonstrate a critical impact on code in production for an asset not in scope, DeGate encourages you to submit your bug report using the “primacy of impact exception” asset.
Impacts in Scope
(For Blockchain/DLTR and Smart Contracts Only) This program is considered to be governed by Primacy of Impact. For more information on what this means visit: Best Practice - Primacy of Impact vs Primacy of Rules.
Impacts are based on the Immunefi Vulnerability Severity Classification System V2.2.
At Immunefi, we classify bugs on a simplified 5-level scale:
Impacts in scope
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.
- Direct theft of any user funds, whether at-rest or in-motionCriticalImpact
- Permanent freezing of fundsCriticalImpact
- Made DeGate have to go into Exodus ModeCriticalImpact
- Protocol insolvencyCriticalImpact
- Use a Proving Key that does not match the contract registration Verifying Key to generate a zero-knowledge proof and pass the contract verificationCriticalImpact
- The amount of tokens in the L2 is inconsistent with that of the L1, except for Non-Standard tokensCriticalImpact
- Climbing blocks fails to recovery the asset treeCriticalImpact
- Temporary freezing of funds for a minimum of 15 daysHighImpact
- Consume token ID, prevent new token from registeringHighImpact
- Steal trading fee or gas feeHighImpact
- Prevent new users from registering, through abnormal consumption of L2 accounts, etc.HighImpact
- The account cannot be used, through abnormal consumption of the L2 storage area, etc.HighImpact
- Smart contract unable to operate due to lack of token funds for a minimum of 24 hoursMediumImpact
- Theft of unclaimed yieldMediumImpact
- Permanent freezing of unclaimed yieldMediumImpact
- Block stuffing for profitMediumImpact
- Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)MediumImpact
- Theft of gasMediumImpact
- Unbounded gas consumptionMediumImpact
- Circuit fails to work correctly, but doesn’t lose valueLowImpact
- Contract fails to deliver promised returns, but doesn't lose valueLowImpact
Websites and Applications
- Execute arbitrary system commandsCriticalImpact
- Retrieve sensitive data/files from a running server such as: /etc/shadow, database passwords, blockchain keys (this does not include non-sensitive environment variables, open source code, or usernames)CriticalImpact
- Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as: Changing registration information, Making trades, Withdrawals, etc.CriticalImpact
- Direct theft of user fundsCriticalImpact
- Malicious interactions with an already-connected wallet such as: Modifying transaction arguments or parameters, Substituting contract addresses, Submitting malicious transactionsCriticalImpact
- Actual transaction data is abnormal, with abnormal amounts and addresses of transfers and withdrawals.CriticalImpact
- Changing non-sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as: Theme config, Langage config, Post only config, Traded pairsMediumImpact
- Redirecting users to malicious websites (Open Redirect)MediumImpact
- Changing details of other users (including modifying browser local storage) without already-connected wallet interaction and with significant user interaction such as: Iframing leading to modifying the backend/browser state (demonstrate impact with PoC)LowImpact
- Taking over broken or expired outgoing links such as: Social media handles, etc.LowImpact
- Temporarily disabling user to access target site, such as: Locking up the victim from login, Cookie bombing, etc.LowImpact
Out of Scope & Rules
The following impacts and attack vectors are excluded from rewards by default for all Immunefi bug bounty programs:
- Attacks that the reporter has already exploited themselves, leading to damage
- Attacks requiring access to leaked keys/credentials
- Attacks requiring access to privileged addresses (governance, strategist), except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible
- Broken link hijacking is out of scope
Smart Contracts and Blockchain/DLT
- Basic economic governance attacks (e.g. 51% attack)
- Lack of liquidity
- Best practice critiques
- Sybil attacks
- Centralization risks
- Impacts involving balance changes and authority freezes caused by the token contract itself, such as rebase tokens
- Impacts involving the need to use an unreasonable amount of valueless testnet ETH for block stuffing to force entry into Exodus Mode, register a significant number of tokens and accounts to occupy storage, and execute other economically secure attacks. An unreasonable amount is considered as over 300 ETH and a reasonable amount is 50 ETH or less. Any amount in between may be considered as valid or downgraded based on the other factors of the bug report.
Websites and Apps
- Theoretical impacts without any proof or demonstration
- Content spoofing / Text injection issues
- Captcha bypass using OCR
- CSRF with no security impact (logout CSRF, change language, etc.)
- Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”)
- Server-side information disclosure such as IPs, server names, and most stack traces
- Vulnerabilities used to enumerate or confirm the existence of users or tenants
- Vulnerabilities requiring unlikely user actions
- URL Redirects (unless combined with another vulnerability to produce a more severe vulnerability)
- Lack of SSL/TLS best practices
- Attacks involving DDoS
- Attacks requiring privileged access from within the organization
- SPF records for email domains
- Feature requests
- Best practices
- Vulnerabilities primarily caused by browser/plugin defects
- Any vulnerability exploit requiring CSP bypass resulting from a browser bug
The following activities are prohibited by this bug bounty program. Violation of these rules can result in a temporary suspension or permanent ban from the Immunefi platform at the sole discretion of the Immunefi team, which may also result in: 1) the forfeiture and loss of access to all bug submissions, and 2) zero payout.
Please note that Immunefi has no tolerance for spam/low-quality/incomplete bug reports, “beg bounty” behavior, and misrepresentation of assets and severity. Immunefi exists to protect the global crypto community, not facilitate grift.
- Attempting phishing or other social engineering attacks against our employees and/or customers
- Any testing with third party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
- Any denial of service attacks
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty
- Any other actions prohibited by the Immunefi Rules. These rules are subject to change at any time.