CapyFi
Bounty Range
$1,000 - $1,000,000
external program
CapyFi
CapyFi is an algorithmic decentralized finance protocol built on the Ethereum network that allows users to lend and borrow cryptocurrency assets. Suppliers provide liquidity to the market to earn interest, while borrowers are able to borrow liquidity in an over-collateralized fashion. Capyfi's protocol design and architecture references Compound v2, a proven and audited protocol.
For more information about CapyFi, please visit https://capyfi.com/.
CapyFi provides rewards in USDC on ETH, denominated in USD.
Smart Contract
| Severity | Maximum | Minimum |
|---|---|---|
| Critical | $1,000,000 | $50,000 |
| High | $50,000 | $10,000 |
| Medium | $10,000 | $5,001 |
| Low | $5,000 | $1,000 |
Websites and Applications
| Severity | Reward |
|---|---|
| Critical | Flat: $8,000 |
| High | Flat: $3,000 |
| Medium | Flat: $1,500 |
Mainnet assets: Reward amount is 10% of the funds directly affected up to a maximum of $1,000,000. Minimum reward to discourage security researchers from withholding a bug report: $50,000.
Reward Calculation for Critical Level Reports
For critical smart contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD $1M. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD $50,000 is to be rewarded in order to incentivize security researchers against withholding a critical bug report.
For critical web/apps bugs, reports will be rewarded with up to USD $10,000, only if the impact leads to:
All other impacts that would be classified as Critical would be rewarded within a range of USD $4,001 to USD $10,000 depending on the impact. The rest of the severity levels are paid out according to the Impact in Scope table.
Repeatable Attack Limitations
Reward Calculation for High Level Reports
High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties are rewarded within a range of USD $10,000 to USD $50,000 with the reward calculated based on 100% of the funds at risk, though capped at the maximum high reward.
In the event of temporary freezing, the reward doubles from the full frozen value for every additional 24h that the funds are temporarily frozen, up until a max cap of the high reward.
Reward Payment Terms
Payouts are handled by the CapyFi team directly and are denominated in USD. However, payments are done in USDC on ETH.
The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability.
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.
CapyFi will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:
Security researchers who wish to participate must adhere to the rules of engagement set forth in this program and cannot be:
CapyFi adheres to Category 2: Notice Required. This Policy determines what information researchers are allowed to make public from their submitted bug reports.
CapyFi adheres to the Primacy of Impact for the following impacts:
Primacy of Impact means that the impact is prioritized rather than a specific asset. This encourages security researchers to report on all bugs with an in-scope impact, even if the affected assets are not in scope.
When submitting a report on Immunefi's dashboard, the security researcher should select the Primacy of Impact asset placeholder. If the team behind this project has multiple programs, those other programs are not covered under Primacy of Impact for this program. Instead, check if those other projects have a bug bounty program on Immunefi.
If the project has any testnet and/or mock files, those will not be covered under Primacy of Impact.
All other impacts are considered under the Primacy of Rules, which means that they are bound by the terms and conditions set within this program.
A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules.
Bug reports covering previously-discovered bugs are not eligible for a reward within this program. This includes known issues that the project is aware of but has consciously decided not to "fix", necessary code changes, or any implemented operational mitigating procedures that can lessen potential risk.
Known issues can be found at: https://docs.google.com/spreadsheets/d/1_vAogDWyY3x1bp6NO7NccKWoNACbPybR0OX39fA0LIM/edit?gid=0#gid=0
CapyFi's completed audit reports can be found at: https://drive.google.com/file/d/1fc--zdl1U8LFhysu7FiTgzviIyfPDgGA/view
Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
Audit History:
| Auditor | Link | Completed |
|---|---|---|
| Coinspect | https://www.coinspect.com/doc/Coinspect%20-%20Smart%20Contract%20Audit%20-%20Capyfi%20-%20v250711.pdf | 11 July 2025 |
| OpenZeppelin | https://www.openzeppelin.com/news/capyfi-audit | 24 July 2025 |
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.
Immunefi has developed feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.