On-chain options enabling volatility trading. Creators of the first Impermanent Gain options
In Scope
| Target | Type | Reward |
|---|---|---|
https://github.com/dverso/smilee-v2-contracts/tree/master/srcSmilee v2 core contracts (contracts out of scope are specified in the following tabs) |
Smart Contract | Bounty |
Out of scope
| Target | Type | Severity |
|---|---|---|
https://github.com/dverso/smilee-v2-contracts/blob/master/src/periphery/MasterChefSmilee.sol |
Smart Contract | None |
https://github.com/dverso/smilee-v2-contracts/blob/master/src/periphery/SimpleRewarderPerSec.sol |
Smart Contract | None |
https://github.com/dverso/smilee-v2-contracts/blob/master/src/periphery/IGAccessNFT.sol |
Smart Contract | None |
https://github.com/dverso/smilee-v2-contracts/tree/master/src/testnet |
Smart Contract | None |
IN-SCOPE: SMART CONTRACT VULNERABILITIES
We are looking for evidence and reasons for incorrect behavior of the smart contract, which could cause unintended functionality:
- Stealing or loss of funds
- Unauthorized transaction
- Transaction manipulation
- Attacks on logic (behavior of the code is different from the business description)
- Reentrancy
- Reordering
- Over and underflows
OUT OF SCOPE: SMART CONTRACT VULNERABILITIES
- Theoretical vulnerabilities without any proof or demonstration
- Old compiler version
- The compiler version is not locked
- Vulnerabilities in imported contracts
- Code style guide violations
- Redundant code
- Gas optimizations
- Best practice issues
- Issues related to usage of ERC20 tokens that are upgreadable, pausable, rebasing, with fee-on-transfer, exotic
- Centralization issues generated
- Financial issues related to impact of DEX swap fees and slippage on vault/ DVP accounting/ solvency
- Issues related to manipulation of oracle prices and / or DEX prices
- Issues related with stale, wrong, negative oracles data
- Issues already known in previous public audit (Trust Security)
- Avoid using web application scanners for automatic vulnerability searching which generates massive traffic
- Make every effort not to damage or restrict the availability of products, services, or infrastructure
- Avoid compromising any personal data, interruption, or degradation of any service
- Don’t access or modify other user data, localize all tests to your accounts
- Perform testing only within the scope
- Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam
- Don’t spam forms or account creation flows using automated scanners
- In case you find chain vulnerabilities we’ll pay only for vulnerability with the highest severity.
- Don’t break any law and stay in the defined scope
- Any details of found vulnerabilities must not be communicated to anyone who is not a HackenProof Team or an authorized employee of this Company without appropriate permission
- Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization
- No vulnerability disclosure, including partial is allowed for the moment.
- Please do NOT publish/discuss bugs
We are happy to thank everyone who submits valid reports which help us improve the security. However, only those that meet the following eligibility requirements may receive a monetary reward:
- You must be the first reporter of a vulnerability.
- The vulnerability must be a qualifying vulnerability
- Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com
- You must send a clear textual description of the report along with steps to reproduce the issue, include attachments such as screenshots or proof of concept code as necessary.
- You must not be a former or current employee of us or one of its contractor.
- ONLY USE the EMAIL under which you registered your HackenProof account (in case of violation, no bounty can be awarded)
- Provide detailed but to-the point reproduction steps