Triaged by Immunefi
PoC Required
KYC required
Rewards
Rewards by Threat Level
Mainnet assets:
Reward amount is 10% of the funds directly affected up to a maximum of:
$1,500,000Reward 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 $1,500,000. 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 $150,000 is to be rewarded in order to incentivize security researchers against withholding a critical bug report. There needs to be an absolute minimum of USD 50 000 at risk in order to be considered Critical. In any other case the impact will be downgraded to High.
For critical web/apps bugs, reports will be rewarded with $50,000, only if the impact leads to:
- A loss of funds involving an attack that does not require any user action
- Private key or private key generation leakage leading to unauthorized access to user funds
All other impacts that would be classified as Critical would be rewarded a flat amount of $20,000. The rest of the severity levels are paid out according to the Impact in Scope table.
Repeatable Attack Limitations
- If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attack will be considered for a reward.
Reward Calculation for High Level Reports
High impacts concerning theft/permanent freezing of unclaimed yield/royalties are rewarded within a range of $10,000 to $100,000 with the reward calculated based on 100% of the funds at risk, though capped at the maximum high reward.
If the duration of temporary freezing is 9,000 blocks or less, then the severity level will be reduced to Medium if the amount is equal to or greater than USD 100 000. If not, the severity level will be downgraded to Low. There needs to be a minimum of USD 5 000 at risk in order for a report to be considered High.
Reward Payment Terms
Payouts are handled by the Kamino team directly and are denominated in USD. However, payments are done in USDC on SOL.
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.
Program Overview
Kamino is a first-of-its-kind DeFi protocol that unifies Lending, Liquidity, and Leverage into a single, secure DeFi product suite.
For more information about Kamino, please visit https://kamino.finance/.
Kamino provides rewards in USDC on SOL, denominated in USD. For more details about the payment process, please view the Rewards by Threat Level section further below.
KYC Requirement
Kamino will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:
- Full name
- Date of birth
- Proof of address (either a redacted bank statement with address or a recent utility bill)
- Copy of Passport or other Government issued ID
Primacy of Impact vs Primacy of Rules
Kamino adheres to the Primacy of Impact for the following impacts:
- Smart Contract — Critical
- Smart Contract — High
- Website & Application — Critical
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.
For more information, please see Best Practices: Primacy of Impact
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.
Proof of Concept (PoC) Requirements
A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules.
Previous Audits
Kamino’s completed audit reports can be found at https://github.com/Kamino-Finance/audits. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
KYC required
The submission of KYC information is a requirement for payout processing.
Proof of Concept
Proof of concept is always required for all severities.
Responsible Publication
Category 3: Approval Required
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.