Duet Finance
Duet protocol (Duet) is a Multi-chain synthetic asset protocol that sharpens all assets for use in the blockchain world. A duet in music refers to a piece of music where two people play different parts or melodies. Similarly, Duet protocol allows traders to replicate the real-world tradable assets in a decentralised finance ecosystem.
PoC required
Rewards
Rewards by Threat Level
Mainnet assets:
Reward amount is 10% of the funds directly affected up to a maximum of:
$10,000Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.
All Smart Contract bug reports require a PoC and a suggestion for a fix to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required.
The following vulnerabilities are not eligible for a reward:
In contract 0x014127E127C6788BaDaE75Ba213a58Ac22944c82 , a potential sandwith attack may occur when swap because we ignore slippage control. Some tokens may be left on contract 0x014127E127C6788BaDaE75Ba213a58Ac22944c82 when transferring tokens to Liquidity Pool or BNB to Liquidity Pool.
All vulnerabilities marked in the BlockSec security review and Peckshield security review 1st report , Peckshield security review 2nd report are not eligible for a reward.
Payouts are handled by the Duet Finance team directly and are denominated in USD. However, payouts are done in USDT and bDUET (which is abbreviation for bonded DUET or you can simply understand unvested DUET, and the sessions here that will mature in less than half a year, specific terms to be negotiable case by case), with the choice of the ratio at the discretion of the team.
Program Overview
Duet protocol (Duet) is a Multi-chain synthetic asset protocol that sharpens all assets for use in the blockchain world. A duet in music refers to a piece of music where two people play different parts or melodies. Similarly, Duet protocol allows traders to replicate the real-world tradable assets in a decentralised finance ecosystem.
For more information about Duet Finance, please visit https://duet.finance/.
This bug bounty program is focused on their smart contracts and is focused on preventing:
- Loss of user funds staked (principal) by freezing or theft
- Loss of governance funds
- Theft of unclaimed yield
- Freezing of unclaimed yield
- Smart contract gas drainage
- Smart contract fails to deliver promised returns, but doesn’t lose value
- Incorrect polling actions
- Leak of user data
- Deletion of user data
- Access to sensitive pages without authorization
KYC not required
No KYC information is required for payout processing.
Proof of Concept
Proof of concept is always required for all severities.
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.