Impacts only apply to assets in active use by the project like contracts on mainnet or web/app assets used in production. Any impact that applies to assets not in active use, like test or mock files, are out-of-scope of the bug bounty program unless explicitly mentioned as in-scope. 

__Smart Contracts__ 

- __Smart Contracts - PoC__, Smart Contract bug reports are to include a runnable Proof of Concept (PoC) in order to prove impact.  
- For more information on PoCs please visit: [Proof of Concept (PoC) Guidelines and Rules](https://immunefisupport.zendesk.com/hc/en-us/articles/9946217628561-Proof-of-Concept-PoC-Guidelines-and-Rules)
- All smart contracts of IPOR can be found at: [https://github.com/IPOR-Labs](https://github.com/IPOR-Labs)

Whitehats are highly encouraged to review any potential subdomains and what specific port(s) are in scope. Even though the domain may be the same, different ports may point to different assets.  

__Dev Environment and Documentation:__

IPOR has included dev documentation and/or instructions to help in reviewing code and exploring for bugs:
- [https://docs.ipor.io/](https://docs.ipor.io/)
- [https://github.com/IPOR-Labs/ipor-protocol/blob/main/README.md](https://github.com/IPOR-Labs/ipor-protocol/blob/main/README.md)
- [https://github.com/IPOR-Labs/ipor-power-tokens/blob/main/README.md](https://github.com/IPOR-Labs/ipor-power-tokens/blob/main/README.md)

__Impacts to other assets:__

Hackers are encouraged to submit issues outside of the outlined Impacts and Assets in Scope. 

If whitehats can demonstrate a critical impact on code in production for an asset not in scope, IPOR encourages you to submit your bug report using the “primacy of impact exception” asset. 

__Impacts in Scope:__

(For Blockchain/DLTR and Smart Contracts Only) This program is considered to be governed by Primacy of Impact. For more information on what this means visit: [Best Practice - Primacy of Impact vs Primacy of Rules.](https://immunefisupport.zendesk.com/hc/en-us/articles/12340245635089-Best-Practices-Primacy-of-Impact) 

Impacts are based on the [Immunefi Vulnerability Severity Classification System V2.2.](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-2/)

At Immunefi, we classify bugs on a simplified 5-level scale:
- Critical
- High
- Medium
- Low
- None

IPOR refers to a set of protocols, smart contracts, and software that forms a set of Decentralized Applications (DApps) for Decentralized Finance (DeFi) focused on interest rate derivatives. The core IPOR infrastructure consists of three main parts: the IPOR Index (Index), Liquidity Pools with an Automated Market Maker (AMM) and Asset Management smart contracts.

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

Permanent freezing of funds

Protocol insolvency

Theft of unclaimed yield

Permanent freezing of unclaimed yield

Smart contract unable to operate due to lack of token funds for 24 hours

Contract fails to deliver promised returns, but doesn't lose value

Please review how rewards are distributed 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 system with separate scales for Smart Contracts and Websites/Apps.

__Payouts and Payout Requirements:__

Payouts are handled by the IPOR team directly and are denominated in USD. However, payouts are done in USDC and IPOR. For critical vulnerability, IPOR DAO will pay 50% in USDC and 50% in IPOR tokens.  IPOR commits to honoring payouts according to the terms set out in this program at the time of report submission, and to treat this program as the agreement and source of truth concerning bug reports and responsible disclosures. 

| Impact     | Criteria for assessing economic damage     |
| ---------- | ---------- |
| Critical       | Risk Ratio = Funds at Risk / ( IPOR TVL). If the risk ratio is at or below 0.5, the payout is calculated linearly between 0$ and 25K. If the risk ratio is above 0.5, the payout is calculated linearly between USD $25K and USD $100K; with a maximum cap of $100K. In the event that the funds at risk is greater than the IPOR TVL, the maximum reward will not exceed USD $100K.

For the purposes of determining report validity, this is a Primacy of Impact program. 

Learn more about report validity best practices here: [Best Practice - Primacy of Impact vs Primacy of Rules.](https://immunefisupport.zendesk.com/hc/en-us/articles/12340245635089-Best-Practices-Primacy-of-Impact) 

__KYC Requirements:__

IPOR __does not__ have a Know Your Customer (KYC) requirement for bug bounty payouts. 

__Audit Discoveries and Known Issues:__

Bug reports covering previously-discovered bugs are not eligible for any reward through the bug bounty program. If a bug report covers a known issue, it may be rejected together with proof of the issue being known before escalation of the bug report via Immunefi. 

__Description of known issue:__
- IPOR index value manipulation through AAVE & Compound
- reports reported via github [https://github.com/IPOR-Labs/ipor-audit-reports](https://github.com/IPOR-Labs/ipor-audit-reports)
- The issue with liquidity pools amount equals zero
- asset management relies on the published token exchange rate (gas optimization)
- when opening swaps the asset management holdings are calculated without the interest (gas optimisation)

IPOR

Resources & Documentation