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.
PoC required
Rewards
Rewards by Threat Level
Mainnet assets:
Reward amount is 10% of the funds directly affected up to a maximum of:
$200,000Rewards 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.
Program Overview
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.
KYC not required
No KYC information is required for payout processing.
Proof of Concept
Proof of concept is always required for all severities.
Prohibited Activities
- Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
- 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 that are executed against project assets
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty
- Any other actions prohibited by the Immunefi Rules
Feasibility Limitations
The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity.
Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.
336.6k