Kiln (dApp/Infra)
Kiln is a yield product platform you can use to stake or deposit into defi directly, wether you are custodian of your funds or you integrate us in your non-custodial platform.
Triaged by Immunefi
PoC Required
KYC required
Rewards
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3. Reward Calculation for Critical Level Reports
For critical web/apps bugs, reports will be rewarded to 10% of the impacted TVL, up to a maximum of USD 100 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 or stake
All other impacts that would be classified as Critical would be rewarded a flat amount of USD 8 000. The rest of the severity levels are paid out according to the Impact in Scope table.
Reward Payment Terms
Payouts are handled by the Kiln Infrastructure + Web team directly and are denominated in USD. However, payments are done in USDC on Ethereum.
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
Kiln is a yield product platform you can use to stake or deposit into defi directly, wether you are custodian of your funds or you integrate us in your non-custodial platform.
We enable you or your clients to deposit crypto assets, manually or programmatically, while maintaining custody of your funds in your existing solution, such Fireblocks, Copper, or Ledger.
This program is for Kiln’s Web/App and Infrastructure assets. For bug reports for their Smart Contracts, please visit their other program:
- Kiln DeFi: https://immunefi.com/bug-bounty/kiln-defi/information/
- Kiln On-Chain V1: https://immunefi.com/bug-bounty/kiln-on-chain-v1/information/#top
- Kiln On-Chain V2: https://immunefi.com/bug-bounty/kiln/information/
For more information about Kiln Infrastructure + Web, please visit https://www.kiln.fi/.
Kiln Infrastructure + Web provides rewards in USDC on Ethereum, denominated in USD. For more details about the payment process, please view the Rewards by Threat Level section further below.
__KYC Requirement __
Kiln Infrastructure + Web will be requesting KYC information in order to pay for successful bug submissions. The following information will be required: If the claim comes from an individual:
- The first names, surnames, date and place of birth of the person concerned
- A Valid ID
If the claim comes from a business:
- Legal form, name, registration number and address of the registered office
- Valid certificate of incorporation
- List of shareholders/directors
Primacy of Impact vs Primacy of Rules
Kiln Infrastructure + Web adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms and conditions stated within this page.
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.
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.