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

Yield Aggregator
Maximum Bounty
Live Since
12 January 2023
Last Updated
31 March 2024
  • PoC required

Submit a Bug

Rewards by Threat Level

Smart Contract
Up to USD $100,000
USD $7,500
USD $1,000
Websites and Applications
USD $1,000

Rewards are distributed according to the impact of the vulnerability based on the 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:

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.

Program Overview

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

We currently have three strategies: One if you are bearish, and want to earn money in case the market goes down, another one in case the market goes up and one if you don't know the market direction but you know that volatility will be present.

The strategy also assumes that Lidoand AAVE are a reputable source of a base yield on ETH.

For more information about Pods, please visit https://docs.pods.finance/.

KYC not required

No KYC information is required for payout processing.

Prohibited Activities

Default prohibited activities
  • Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
  • 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 that are executed against project assets
  • Automated testing of services that generates significant amounts of traffic
  • Public disclosure of an unpatched vulnerability in an embargoed bounty
  • Any other actions prohibited by the Immunefi Rules

Feasibility Limitations

The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.