
Kiln On-Chain v1
Bounty Range
$5,000 - $1,000,000
external program


Bounty Range
$5,000 - $1,000,000
external program
Kiln On-Chain (v1) enables non-custodial platforms to propose an ETH staking offer where users can stake on dedicated validators while remaining the only one able to access their staked assets.
The goal of these Ethereum Smart Contracts is to enable:
This Bug Bounty is focused on the Staking Smart Contracts only, all items regarding dApps or validation infrastructure are out of scope.
Smart Contract - Critical
Smart Contract - High
Smart Contract - Medium
For critical Smart Contract vulnerabilities that result in direct theft or permanent freezing of funds, the reward amount is 10% of the funds directly affected up to a maximum of USD 1,000,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 100,000 is to be rewarded in order to incentivize security researchers against withholding a bug report.
In cases of repeatable attacks for smart contract bugs, only the first attack will be counted, regardless of whether the smart contract is upgradable, pausable, or killable.
For high Smart Contract vulnerabilities that result in direct theft or permanent freezing of unclaimed yield or commission, or the temporary freezing of unclaimed yield for more than 24hrs, the reward amount will be capped at 100% of the funds affected, up to a maximum of USD 100,000. However, a minimum reward of USD 20,000 is to be rewarded in order to incentivize security researchers against withholding a bug report.
Payouts are handled by the Kiln team directly and are denominated in USD. However, payments are done in USDC.
Researchers who submit valid vulnerability reports agree to adhere to the following responsible disclosure process:
Kiln has provided completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.
A PoC is required for the following severity levels:
All PoCs submitted must comply with the Immunefi-wide PoC Guidelines and Rules. Bug report submissions without a PoC when a PoC is required will not be provided with a reward.
The provision of KYC is required to receive a reward for this bug bounty program where the following information will be required to be provided:
If the claim comes from an individual:
If the claim comes from a business:
KYC information is only required on confirmation of the validity of a bug report.
Kiln adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms stated in this page.
Kiln commits to providing Known Issue Assurance to bug submissions through their program. This means that Kiln will either disclose known issues publicly or at the very least privately via a self-reported bug submission in order to allow for a more objective and streamlined mediation process to prove that an issue is known. Otherwise, assuming the bug report itself is valid, it would result in the bug report being considered in-scope and due 100% of the reward with respect to the bug bounty program terms.
Kiln has satisfied the requirements for the Immunefi Standard Badge, which is given to projects that adhere to best practices.
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 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.