IOP | Ionic
Immunefi’s Invite Only Program is a form of Boost which is exclusively accessible to a select group of security researchers who have been specifically invited to participate based on their expertise and skills. These researchers receive a guaranteed fee for participation and additional reward for every valid bug found. Project assets are only visible to the whitelisted researchers.
Status
This Bug Bounty Boost Is Over
Boost cards for security researchers with paid reports are available here.
Rewards by Threat Level
The following reward terms are a summary, for the full details read our Ionic IOP Reward Distribution Terms.
Each participating whitehat will receive a guaranteed reward $2,000.
A reward pool of $4,000 USD will be distributed among participants. If no valid bugs are found then the reward pool will be distributed between whitehats or returned to the project at Immunefi’s discretion.
For this Invite Only Program, duplicates and private known issues are valid for a reward.
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.
Rewards will be distributed all at once based on Immunefi’s distribution formula after the event has concluded and the final bug reports have been resolved.
Insight Rewards Payment Terms
Insight Rewards: Portion of the Rewards Pool
- The "Insight" severity was introduced on Boost & Attackathon programs to recognize contributions that extend beyond identifying immediate vulnerabilities. Currently, it's not an option to select the Insight severity when submitting a report. However, our team or program will designate it accordingly if applicable. "Insights" underscores our commitment to valuing all types of contributions that contribute to a more secure environment and will always be rewarded. View more information about Insights
Program Overview
Immunefi’s Invite Only Program is a form of Boost which is exclusively accessible to a select group of security researchers who have been specifically invited to participate based on their expertise and skills. These researchers receive a guaranteed fee for participation and additional reward for every valid bug found. Project assets are only visible to the whitelisted researchers.
Ionic introduces a new feature. It consists of leveraging positions of the lending platform by repeatedly borrowing and supplying by looping over the assets. The main code of the project is a Compound/Rari fork, but the in-scope feature is completely unique.
For more information about Ionic, please visit https://www.ionic.money/.
Ionic provides rewards in USDC, denominated in USD.
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
- 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.