All smart contracts of Opyn: Squeeth can be found at [https://github.com/opynfinance/squeeth-monorepo](https://github.com/opynfinance/squeeth-monorepo). However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

Opyn builds DeFi native derivatives and options infrastructure that allow users and protocols to buy, sell, and create options, and utilize brand new primitives like squeeth. DeFi enthusiasts and projects alike rely on Opyn’s smart contracts and interface to hedge themselves against DeFi risks and take positions on different cryptocurrencies.

Loss of user funds staked (principal) by freezing or theft

Execute arbitrary system commands

Retrieve sensitive data/files from a running server such as /etc/shadow, database passwords, and blockchain keys(this does not include non-sensitive environment variables, open source code, or usernames)

Taking down the application/website

Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as, changing registration information, commenting, voting, making trades, withdrawals, etc

Subdomain takeover with already-connected wallet interaction

Direct theft of user funds

Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactions

Theft of unclaimed yield

Freezing of unclaimed yield

Temporary freezing of funds for any amount of time

Smart contract gas drainage

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/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 with an end-effect impacting an asset-in-scope in order to be considered for a reward. Critical and High severity smart contract bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward

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 of __USD 25 000__ for Critical bug reports.

The following impacts are considered to be out-of-scope of this bug bounty program:
  - Economic TWAP manipulation 
  - System insolvency if due to economic factors / market movements

If your attack requires orders of magnitude more funds than profits, you can submit but we'll evaluate on a case-by-case basis.

Critical payouts by Sherlock will only be paid out for critical bugs that would result in a loss of funds and can be executed profitably, and this then excludes Sherlock critical bounty payout for temporary freezing bugs.

Payouts are handled by the __Opyn__ team directly and are denominated in USD. However, payouts are done in __USD__, __USDC__, __DAI__ or __ETH__. Critical severity smart contract rewards will be paid out by Sherlock with their bug bounty matching program and are done in __USDC__.

Opyn: Squeeth

Resources & Documentation