Genius Yield
Genius Yield is the all-in-one DeFi platform, that combines an order-book decentralized exchange (DEX) with an AI-powered yield optimizer, built from the ground up on the Cardano blockchain and designed to take advantage of benefits provided by Cardano’s EUTxO smart contracts, such as security, determinism, parallelism, scalability, and composability.
PoC required
Rewards by Threat Level
Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below.
Reward Calculation for Critical Level Reports
For critical smart contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD $25,000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD $15,000 is to be rewarded in order to incentivize security researchers against withholding a critical bug report.
Critical website and application bug reports will be rewarded with USD 15,000, only if the impact leads to a direct loss in funds involving an attack that does not require any user action at all. An impact of minting tokens on-chain beyond intended activity without requiring any user action would also be rewarded this amount due to the undesired dilution of existing circulating tokens. All other impacts that would be classified as Critical, or an impact resulting in a theft of funds that does not fall under this definition, would be rewarded USD 10,000.
Reward Calculation for High Level Reports
For high smart contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD $10,000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD $6,000 is to be rewarded in order to incentivize security researchers against withholding a critical bug report.
Repeatable Attack Limitations
If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attack will be considered for a reward. This is because the project can mitigate the risk of further exploitation by upgrading or pausing the component where the vulnerability exists. The reward amount will depend on the severity of the impact and the funds at risk.
Proof of Concept (PoC) Requirements
A PoC is required for the following severity levels:
- Website and Applications, Critical
- Website and Applications, High
- Smart Contract, Critical
- Smart Contract, High
All PoCs submitted must comply with the Immunefi-wide PoC Guidelines and Rules. Bug report submissions without a PoC, when a PoC is required, will not be provided with a reward.
Reward Payment Terms
Payouts are handled by the Genius Yield team directly and are denominated in USD. However, payments are done in GENS.
The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability. For avoidance of doubt, if the reward amount is USD 5,000 and the average price is USD 0.20 per token, then the reward will be 25,000 units of GENS token.
Program Overview
Genius Yield is the all-in-one DeFi platform, that combines an order-book decentralized exchange (DEX) with an AI-powered yield optimizer, built from the ground up on the Cardano blockchain and designed to take advantage of benefits provided by Cardano’s EUTxO smart contracts, such as security, determinism, parallelism, scalability, and composability.
The overarching objective is to democratize Decentralized Finance by providing an all-in-one, easy-to-use solution, and thus making this new domain accessible to everyone.
Genius Yield aims to provide a high level of security for their users. This bug bounty program offers the possibility for whitehats to report their findings and help us secure our DEX.
For more information about Genius Yield, please visit https://www.geniusyield.co/.
Genius Yield provides rewards in GENS. For more details about the payment process, please view the Rewards by Threat Level section further below.
Responsible Publication
Genius Yield adheres to category 3: Approval Required. This Policy determines what information whitehats are allowed to make public from their submitted bug reports. For more information about the category selected, please refer to our Responsible Publication page.
Primacy of Impact vs Primacy of Rules
Genius Yield adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms stated in this page.
Known Issue Assurance
Genius Yield commits to providing Known Issue Assurance to bug submissions through their program. This means that Genius Yield will either disclose known issues publicly or at the very least privately via a self-reported bug submission in order to allow for a more objective and streamlined mediation process to prove that an issue is known. Otherwise, assuming the bug report itself is valid, it would result in the bug report being considered in-scope and due 100% of the reward with respect to the bug bounty program terms.
Previous Audits
Genius Yield has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.
KYC not required
No KYC information is required for payout processing.
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.