Tranchess

Tranchess is a yield enhancing asset tracker with varied risk-return solutions. Tranchess provides a different risk/return matrix out of a single main fund that tracks a specific underlying asset.

More information about Tranchess can be found on their website, https://tranchess.com/.

This bug bounty program is focused around its smart contracts and app and is mostly concerned with the prevention of the loss of user funds.

Rewards for Smart Contract vulnerabilities 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 web/app bug reports must come with a PoC in order to be considered for a reward.

Vulnerability reports concerning rounding errors with an effect of less than the equivalent of USD 0.01 are not eligible for a reward. Additionally, vulnerability impacts of the Exchange smart contract resulting in “contract consumes unbounded gas”, classified as Medium in the Immunefi Vulnerability Severity Classification System, is not eligible for a reward as it is by design.

Critical vulnerabilities are capped at 10% of economic damage, primarily taking into consideration the funds at risk, but also factoring in PR and branding considerations, at the discretion of the team.
However, there is a minimum reward of USD 50 000.

Payouts are handled by the Tranchess team directly and are denominated in USD. However, payouts are done in USDC.

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