Tribe DAO

The Tribe DAO consists of Rari Capital and Fei Protocol. Rari Capital has launched a series of protocols such as Fuse and Vaults and Fei Protocol maintains an algorithmic stablecoin. Together, these two protocols are working on various DeFi primitives together and now share one treasury.

The Tribe DAO builds and operates a robust network of financial services for digitally-native organizations. For more information about Tribe DAO, please visit https://rari.capital/ and https://fei.money, or join the Rari Capital discord: https://discord.gg/bhTrEfcZuH and the Fei Protocol discord: https://discord.gg/jXvTEBpKEQ. In the future, there will be a Tribe DAO focused website.

This proposal unifies the previous bug bounty programs that both Rari and Fei offered, and incentivizes white hats to identify and alert the DAO on any potential vulnerabilities. This benefits the users, PCV deployments, and the TRIBE token holders.

For more information about Tribe DAO, please visit https://rari.capital/ and https://fei.money. In the future, there will be a Tribe DAO focused website.

This bug bounty program is focused on their smart contracts, website and app and is focused on preventing:

• Any governance voting result manipulation
• Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
• Permanent freezing of funds
• Taking Down the application/website
• Redirection of user deposits and withdrawals

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2. This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.

All web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required.

Theft of yield is considered as Medium severity instead of High.

Pool operator error, including the use of unsafe oracles, is considered as out of scope of this program.

Rewards for critical smart contract vulnerabilities are further capped at 10% of economic damage, with the main consideration being the funds affected in addition to PR and brand considerations, at the discretion of the team. However, there is a minimum reward of USD 100 000 for Critical smart contract bug reports.

Payouts are handled by the Tribe DAO directly and are denominated in USD. However, payouts are done in FEI. Additionally, rewards for Critical-level smart contract bug reports have a vesting schedule lasting between 6-24 months, with a minimum of 6 months for rewards up to USD 400 000, and an additional month added for every USD 100 000 tranche, rounded up.

Smart Contract

Websites and Applications

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)
• Pool operator error, including the use of unsafe oracles
• Lack of liquidity
• Best practice critiques
• Sybil attacks
• Centralization risks

Websites and Apps

• Theoretical vulnerabilities without any proof or demonstration
• 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
• Vulnerabilities primarily caused by browser/plugin defects
• Any vulnerability exploit requiring CSP bypass resulting from a browser bug

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