DeXe Protocol

Back to Explore DeXe Protocol DeXe Protocol is an innovative infrastructure of 50+ smart contracts for building and governing effective DAOs. ETH Infrastructure DAO Python Typescript Go Maximum Bounty $500,000 Live Since 23 January 2024 Last Updated 13 November 2024 PoC Required Vault program KYC required Submit a Bug Information Scope Resources Immunefi vault program Funds available $9,149.05 30d Avg. Funds availability $11,684.57 Assets in vault 7.5k DEXE Public vault address 0xF7F19523F8E0254A76aDaA7b8272aa3731297252 Rewards DeXe Protocol provides rewards in USDC on Ethereum , denominated in USD. Rewards by Threat Level Smart Contract Critical Max: $500,000 Min: $10,000 Primacy of Impact High Max: $10,000 Min: $5,000 Primacy of Impact Medium Flat: $1,000 Primacy of Impact Critical Reward Calculation Mainnet assets: Reward amount is 10 % of the funds directly affected up to a maximum of: $500,000 Minimum reward to discourage security researchers from withholding a bug report: $10,000 Rewards Body Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3 . Reward Calculation for Critical Level Reports For critical smart contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 500 000 . The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD 10 000 is to be rewarded in order to incentivize security researchers against withholding a critical bug report. Repeatable Attack Limitations If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attacks within the first hour will be considered for a reward. This is because the project can mitigate the risk of further exploitation by upgrading or pausing the component where the vulnerability exists. The reward amount will depend on the severity of the impact and the funds at risk. For critical repeatable attacks on smart contracts that cannot be upgraded or paused, the project will consider the cumulative impact of the repeatable attacks for a reward. This is because the project cannot prevent the attacker from repeatedly exploiting the vulnerability until all funds are drained and/or other irreversible damage is done. Therefore, this warrants a reward equivalent to 10% of funds at risk, capped at the maximum critical reward. Reward Calculation for High Level Reports High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties are rewarded within a range of USD 5 000 to USD 10 000 depending on the funds at risk, capped at the maximum high reward. In the event of temporary freezing, the reward doubles from the full frozen value for every additional 24h that the funds are temporarily frozen, up until a max cap of the high reward. This is because as the duration of the freezing lengthens, the potential for greater damage and subsequent reputational harm intensifies. Thus, by increasing the reward proportionally with the frozen duration, the project ensures stronger incentives for bug disclosure of this nature. Reward Payment Terms Payouts are handled by the DeXe Protocol team directly and are denominated in USD . All medium rewards will be paid out in USDC . All high rewards will be paid out in $DeXe. All critical rewards will be paid out in $DeXe with a 6-month linear vesting schedule. The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability. View impacts in scope Program Overview DeXe Protocol is an innovative infrastructure of 50+ smart contracts for building and governing effective DAOs. For more information about DeXe Protocol, please visit dexe.network DeXe Protocol provides rewards in USDC , denominated in USD . For more details about the payment process, please view the Rewards by Threat Level section further below. KYC Requirement DeXe Protocol will be requesting KYC information in order to pay for successful bug submissions. The following information will be required: Full name Date of birth Proof of address (either a redacted bank statement with address or a recent utility bill) Copy of Passport or other Government issued ID Primacy of Impact vs Primacy of Rules DeXe Protocol adheres to the Primacy of Impact for the following impacts: Smart Contracts: Critical Smart Contracts: High Smart Contracts: Medium Primacy of Impact means that the impact is prioritized rather than a specific asset. This encourages security researchers to report on all bugs with an in-scope impact, even if the affected assets are not in scope. For more information, please see Best Practices: Primacy of Impact When submitting a report on Immunefi’s dashboard, the security researcher should select the Primacy of Impact asset placeholder. If the team behind this project has multiple programs, those other programs are not covered under Primacy of Impact for this program. Instead, check if those other projects have a bug bounty program on Immunefi. If the project has any testnet and/or mock files, those will not be covered under Primacy of Impact. All other impacts are considered under the Primacy of Rules, which means that they are bound by the terms and conditions set within this program. Proof of Concept (PoC) Requirements A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules. Known Issue Assurance DeXe Protocol commits to providing Known Issue Assurance to bug submissions through their program. This means that DeXe Protocol will either disclose known issues publicly, or at the very least, privately via a self-reported bug submission. In a potential scenario of a mediation, this allows for a more objective and streamlined process, in order to prove that an issue is known. Otherwise, assuming the bug report is valid, it would result in the report being considered as in-scope, and due a reward. Previous Audits DeXe Protocol’s completed audit reports can be found in the following links: https://github.com/dexe-network/DeXe-Protocol/blob/master/audits/README.md https://github.com/dexe-network/DeXe-Protocol/blob/master/audits/ambisafe-2023-07-18.pdf https://github.com/dexe-network/DeXe-Protocol/blob/master/audits/ambisafe-2023-11-10.pdf https://github.com/dexe-network/DeXe-Protocol/blob/master/audits/certik-2023-05-04.pdf https://github.com/dexe-network/DeXe-Protocol/blob/master/audits/cyfrin-2023-11-10.pdf https://github.com/dexe-network/DeXe-Protocol/blob/master/audits/hacken-2023-05-22.pdf Immunefi Standard Badge By adhering to Immunefi’s best practice recommendations, DeXe Protocol has satisfied the requirements for the Immunefi Standard Badge . KYC required The submission of KYC information is a requirement for payout processing. Participants must adhere to the Eligibility Criteria. Proof of Concept Proof of concept is always required for all severities. Responsible Publication Category 3: Approval Required Prohibited Activities Default prohibited activities Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet Any testing with pricing oracles or third-party smart contracts 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 that are executed against project assets 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 Feasibility Limitations The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report. Chain Rollbacks Pre-Impact Bug Monitoring Attack Investment Amount Attacks With A Financial Risk To The Attacker When Is An Impactful Attack Downgraded To Griefing? Submit a Bug 30d Avg. Funds Availability $11,684.57 Total Assets in Scope 11