All smart contracts of Pods can be found at [https://github.com/pods-finance/yield-contracts](https://github.com/pods-finance/yield-contracts). However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

If a Critical/High severity impact can be caused to any other asset managed by Pods 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.

Pods  is a DeFi structured product. It is similar to Yearn, but with derivatives strategies. Pods currently have principal protected strategies., low-risk strategy. 

Any governance voting result manipulation

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

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

Permanent freezing of funds

Miner-extractable value (MEV)

Protocol insolvency

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

Injecting/modifying the static content on the target application without Javascript (Persistent) such as HTML injection without Javascript, replacing existing text with arbitrary text, arbitrary file uploads, etc.

Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as email or password of the victim, etc.

Improperly disclosing confidential user information such as email address, phone number, physical address, etc.

Subdomain takeover without already-connected wallet interaction

Theft of unclaimed yield

Theft of unclaimed royalties

Permanent freezing of unclaimed yield

Temporary freezing of funds for at least 8 days

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

Smart contract fails to deliver promised returns, but doesn’t lose value

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 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. Explanations and statements are not accepted as PoC and code is required.

Known issues highlighted in the following audit reports are considered out of scope: 
- [https://github.com/pods-finance/yield-contracts/tree/main/audits](https://github.com/pods-finance/yield-contracts/tree/main/audits)

Valid critical vulnerabilities are awarded at 5% of the funds at risk, up to USD __100,000__

Payouts are handled by the __Pods__ team directly and are denominated in USD. However, payouts are done in __USDC__.