Tetu-logo

Tetu

TETU is a DeFi application built on Polygon that implements automated yield farming strategies in order to provide investors with a safe and secure method of receiving high and stable yield on their investments. Tetu's innovative solutions provide automated yield aggregation and distribution through xTETU.

Polygon
Defi
Asset Management
DEX
Lending
Token
Yield Aggregator
Solidity
Maximum Bounty
$2,000
Live Since
30 November 2021
Last Updated
13 November 2024
  • PoC Required

Select the category you'd like to explore

Assets in Scope

Target
Name
TETU Token
Added on
11 February 2022
Target
Name
xTETU Profit Share Token
Added on
11 February 2022
Target
Name
Controller
Added on
11 February 2022
Target
Name
Announcer
Added on
11 February 2022
Target
Name
MintHelper
Added on
11 February 2022
Target
Name
FundKeeper
Added on
11 February 2022
Target
Name
tetuBAL(poly)
Added on
12 November 2022
Name
tetuBAL(eth)
Added on
12 November 2022
Name
BalLocker(eth)
Added on
12 November 2022
Name
BalDepositor
Added on
12 November 2022
Target
Name
veTETU
Added on
16 December 2022
Target
Name
ControllerV2
Added on
15 May 2023

Impacts in Scope

Severity
Critical
Title

Permanent freezing of funds

Severity
Critical
Title

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Severity
Critical
Title

Miner-extractable value (MEV)

Severity
Critical
Title

Protocol insolvency

Out of scope

Program's Out of Scope information
  • Best practice critiques
Default Out of Scope and rules

Smart Contract specific

  • Incorrect data supplied by third party oracles
    • Not to exclude oracle manipulation/flash loan attacks
  • Impacts requiring basic economic and governance attacks (e.g. 51% attack)
  • Lack of liquidity impacts
  • Impacts from Sybil attacks
  • Impacts involving centralization risks

All categories

  • Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
  • Impacts caused by attacks requiring access to leaked keys/credentials
  • Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
  • Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
  • Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
  • Best practice recommendations
  • Feature requests
  • Impacts on test files and configuration files unless stated otherwise in the bug bounty program
  • Impacts requiring phishing or other social engineering attacks against project's employees and/or customers