IPOR

Back to Explore IPOR | 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. Arbitrum ETH Defi AMM Asset Management DEX Derivatives L2 Staking Solidity Maximum Bounty $1,000 Live Since 11 April 2023 Last Updated 24 September 2026 PoC Required Submit a Bug Information Scope Resources Rewards IPOR provides rewards in USDC, IPOR on Ethereum , denominated in USD. Rewards by Threat Level Smart Contract Critical Flat: $1,000 Primacy of Impact Rewards Body Please review how rewards are distributed based on the 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. 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 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) View impacts in scope Program Overview 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. The first type of interest rate derivatives supported by the AMM are Interest Rate Swaps (Swap or IRS). The system also incorporates a Decentralized Autonomous Organization (DAO) and a Treasury in the spirit of decentralization. For more information about IPOR, please visit https://www.ipor.io/ For Whitehats: It is highly recommended that you review the details of this program in full. Although many Bug Bounty programs have standard terms and conditions, each also has their own unique details that are critical to your success. Prior to submitting a report please review the Immunefi Bug Report Template and Best Practices. KYC not required No KYC information is required for payout processing. Proof of Concept Proof of concept is always required for all severities. Prohibited Activities Program's custom prohibited activities The following activities are prohibited by this bug bounty program. Violation of these rules can result in a temporary suspension or permanent ban from the Immunefi platform at the sole discretion of the Immunefi team, which may also result in: 1) the forfeiture and loss of access to all bug submissions, and 2) zero payout. Please note that Immunefi has no tolerance for spam/low-quality/incomplete bug reports, “beg bounty” behavior, and misrepresentation of assets and severity. Immunefi exists to protect the global crypto community, not facilitate grift. 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. Chain Rollbacks Pre-Impact Bug Monitoring Attack Investment Amount Attacks With A Financial Risk To The Attacker When Is An Impactful Attack Downgraded To Griefing? Submit a Bug Total paid 3.8k Med. Resolution Time 12 hours Total Assets in Scope 13