Tranche Finance

Submit a Bug
20 May 2021
Live since
No
KYC required
$23,500
Maximum bounty

Program Overview

Tranche is a decentralized protocol for managing risk. The protocol integrates with any interest accrual token, such as Compound's cTokens and AAVE's aTokens, to create two new interest-bearing instruments, one with a fixed-rate, Tranche A, and one with a variable rate, Tranche B.

The protocol is currently integrated with Compound and charges fees in Dai and USDT. Accrued fees are exchanged for SLICE tokens through Uniswap pools. SLICE holders can vote on protocol parameters and other governance issues, as well as stake their SLICE or SLICE-LP tokens for rewards

Further resources regarding Tranche Finance can be found in their documentation, https://docs.tranche.finance/tranchefinance/.

The bug bounty program is focused around its smart contracts and is mostly concerned with the loss of user funds, economic exploits, and smart contract security risk.

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 web and app bug reports must come with a PoC in order for consideration for a reward. All bug reports without a PoC will be automatically rejected with instructions to provide a PoC.

This bug bounty program has fixed rewards in SLICE. The USD amounts reflected are only estimates. For an up-to-date price of the token, please visit the Tranche Finance Website.

Payouts are handled by the Tranche Finance team directly and are denominated in USD. However, payouts are done in a mix of stablecoins and project tokens.

Smart Contract

Critical
Level
25 000 SLICE (~Up to USD 23,500)
Payout
High
Level
10 000 SLICE (~Up to USD 9,390)
Payout
Medium
Level
5 000 SLICE (~Up to USD 4,695)
Payout
Low
Level
1 000 SLICE (~Up to USD 939)
Payout

Websites and Applications

Critical
Level
2 000 SLICE (~Up to USD 1,878)
Payout
PoC Required
High
Level
1 500 SLICE (~Up to USD 1,408)
Payout
PoC Required
Medium
Level
500 SLICE (~Up to USD 469)
Payout
PoC Required
Low
Level
100 SLICE (~Up to USD 93)
Payout
PoC Required

Assets in scope

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

  • Critical Smart Contract Impact
    Critical
    Impact
  • High Smart Contract Impact
    High
    Impact
  • Medium Smart Contract Impact
    Medium
    Impact
  • Low Smart Contract Impact
    Low
    Impact

Websites and Applications

  • Critical Websites and Applications Impact
    Critical
    Impact
  • High Websites and Applications Impact
    High
    Impact
  • Medium Websites and Applications Impact
    Medium
    Impact
  • Low Websites and Applications Impact
    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

Websites and Apps

  • Theoretical vulnerabilities without any proof or demonstration
  • Content spoofing / Text injection issues
  • Self-XSS
  • 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
  • DDoS vulnerabilities
  • Attacks requiring privileged access from within the organization
  • Feature requests
  • Best practices

The following activities are prohibited by 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