Instructions - open_position_with_metadata

Instructions - set_collect_protocol_fees_authority

Instructions - set_default_protocol_fee_rate

Instructions - set_reward_authority_by_super_authority

Instructions - set_reward_emissions_super_authority

However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

If any Critical/High severity impact can be caused to any other asset managed by Orca that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project.

Orca is one of the first general-purpose AMMs launched on Solana. Users can swap assets, provide liquidity, and earn yield through an easy-to-use interface. Orca has created custom smart contracts for its concentrated liquidity product, [Whirlpools](https://www.orca.so/whirlpools). In traditional AMM liquidity pools, a user provides liquidity across the entire continuous price curve.

Bugs that could temporarily freeze user funds or incorrectly assign value to user funds

Temporary freezing of unclaimed yield for any amount of time

Theft of unclaimed yield

Smart contract unable to operate due to lack of token funds

Block stuffing for profit

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Theft of gas

Unbounded gas consumption

Bugs that freeze user funds or drain the contract's holdings or involve theft of funds without user signatures

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Permanent freezing of funds

Orca Smart Contracts

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, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.

All bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required.

All known issues previously highlighted in the following audits are considered as out of scope: 
  - [Neodyme Audit](https://orca-so.gitbook.io/orca-developer-portal/whirlpools/overview#security-audits)
  - [Kudelski Security](https://drive.google.com/file/d/1u0ja4_3GoogVWVU9prMezDrBaqE5BxdW/view)

Rewards for critical smart contract vulnerabilities can be 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 reward of __USD 100 000__ for Critical smart contract bug reports. 

Payouts are handled by the __Orca__ team directly and are denominated in USD. Payouts of up to __USD 250 000__ are done in __ORCA__ or __USDC__ (SPL Version) at the discretion of the team. Payouts above __USD 250 000__ will be done in __ORCA__ and will be vested monthly over a 12-month period.

Orca

Codebase