Duet Finance

Submit a Bug
14 February 2022
Live since
No
KYC required
$500,000
Maximum bounty

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

Rewards by Threat Level

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. 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.

Smart Contract

Critical
Level
USD $500,000
Payout
PoC Required
High
Level
USD $3,000
Payout
PoC Required
Medium
Level
USD $2,000
Payout
PoC Required
Low
Level
USD $1,000
Payout
PoC Required

Assets in scope

All smart contracts of Duet Finance can be found at https://github.com/duet-protocol/duet-collateral-contracts and https://github.com/duet-protocol/dUSD-minter. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

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.

Smart Contract

  • Loss of user funds staked (principal) by freezing or theft
    Critical
    Impact
  • Loss of governance funds
    Critical
    Impact
  • Governance vote manipulation
    Critical
    Impact
  • Theft of unclaimed yield
    High
    Impact
  • Freezing of unclaimed yield
    High
    Impact
  • Smart contract gas drainage
    Medium
    Impact
  • Smart contract fails to deliver promised returns, but doesn’t lose value
    Low
    Impact

Out of Scope & Rules

The following vulnerabilities are excluded from the rewards for this bug bounty program:

  • 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)

Smart Contracts and Blockchain

  • Incorrect data supplied by third party oracles
    • Not to exclude oracle manipulation/flash loan attacks
  • Basic economic governance attacks (e.g. 51% attack)
  • Lack of liquidity
  • Best practice critiques
  • Sybil attacks
  • Centralization risks

The following activities are prohibited by this bug bounty program:

  • Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
  • 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
  • Automated testing of services that generates significant amounts of traffic
  • Public disclosure of an unpatched vulnerability in an embargoed bounty