Opyn

Opyn builds protocols on Ethereum that allows users to buy, sell, and create options on ERC20s. 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.

Gamma is a capital efficient option protocol that enables sellers to create spreads and other combinations, trade atomically, flash loan mint otokens, assign operators to roll over vaults, create perpetual instruments, and more.

Just like Convexity Protocol(Opyn v1), Gamma protocol enables any user to create option tokens, that represent the right to buy or sell a certain asset in a predefined price (strike price) at expiry.

Opyn is interested in securing its smart contracts and eliminating any risk amounting to loss of user funds.

This bug bounty program is further covered by the Armor Alliance Bug Bounty Challenge.

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. 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.

Critical bug reports are further capped at 10% of economic damage with a minimum payout of USD 50 000.

Payouts are handled by Opyn directly and are denominated in USD. However, payouts up to USD 100 000 are done in USD, USDC, DAIai, or ETH. Payments above USD 100 000 have the remainder paid in ARMOR by the Armor Alliance Bug Bounty Challenge and have a vesting period of up to 24 months.

Addresses for the contracts in scope can be found here - https://opyn.gitbook.io/opyn/getting-started/abis-smart-contract-addresses However, only the contracts listed as in scope in this table are considered for the bug bounty program.

We are especially interested in receiving and rewarding vulnerabilities of the following types:

Smart Contracts/Blockchain:

• Re-entrancy
• Logic errors
  • Including user authentication errors
• Solidity/EVM details not considered
  • Including integer over-/under-flow
  • Including unhandled exceptions
• Trusting trust/dependency vulnerabilities
  • Including composability vulnerabilities
• Oracle failure/manipulation
• Novel governance attacks
• Economic/financial attacks
  • Including flash loan attacks
• Congestion and scalability
  • Including running out of gas
  • Including block stuffing
  • Including susceptibility to frontrunning
• Consensus failures
• Cryptography problems
  • Signature malleability
  • Susceptibility to replay attacks
  • Weak randomness
  • Weak encryption
• Susceptibility to block timestamp manipulation
• Missing access controls / unprotected internal or debugging interfaces

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 that rely on social engineering
• Attacks requiring access to leaked keys/credentials

Smart Contracts/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 attack
• Bugs inCallee Contracts in the Gamma Protocol repo
• Bugs in any third party contract or platform that interacts with Gamma
• Vulnerabilities contingent upon the occurrence of any of the following activities also are outside the scope of this Program:
  • Front end bugs
  • DDOS attack
  • Spamming
• Findings related to non-standard ERC20 tokens might be ineligible as many vulnerabilities might be inserted in non-standard ERC20 tokens on purpose for applying for this bug bounty
• Exploiting the vulnerability in any way, including through making it public or by obtaining a profit (other than a reward under this Program)
• Duplicate vulnerabilities: Only the first reporter will be rewarded (in compliance with the disclosure requirements)
• Findings already known as part of a formal audit or are marked on the repo as issues

The following activities are prohibited by 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
• Disassembly or reverse engineering of binaries for which source code is not published, not including smart contract bytecode
• Public disclosure of an unpatched vulnerability in an embargoed bounty