Kiln On-Chain v1

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:

• Operator to register its validation keys deposit data on the Smart Contract
• Users to deposit on approved and available validation keys
• Manage the Execution and Consensus Layer rewards and exited ETH
• Perform the commission dispatching on these ETH when user performs a withdrawal action

This Bug Bounty is focused on the Staking Smart Contracts only, all items regarding dApps or validation infrastructure are out of scope.

Rewards

Rewards by Threat Level

Smart Contract - Critical

• Max: $1,000,000
• Min: $100,000

Smart Contract - High

• Max: $100,000
• Min: $20,000

Smart Contract - Medium

• Max: $20,000
• Min: $5,000

Critical Reward Calculation

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.

Repeatable Attack Limitations

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.

High Level Reward Calculation

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.

Reward Payment Terms

Payouts are handled by the Kiln team directly and are denominated in USD. However, payments are done in USDC.

Responsible Disclosure

Researchers who submit valid vulnerability reports agree to adhere to the following responsible disclosure process:

• Upon confirmation of a valid vulnerability, Kiln will work diligently to develop and implement a fix.
• Once the fix is deployed to production, Kiln will notify the researcher and initiate a 1-month (30 calendar days) disclosure waiting period.
• During this waiting period, the researcher must maintain strict confidentiality regarding the vulnerability and shall not disclose any information about it to third parties or the public.
• After the 1-month period has elapsed following the production deployment of the fix, the researcher may publicly disclose the vulnerability, provided they have obtained written approval from Kiln regarding the content of the disclosure.
• The researcher agrees to coordinate with Kiln on the timing and content of any public disclosure to ensure all parties are prepared and to minimize potential risks to users.
• If the researcher discovers that the vulnerability has become publicly known before the end of the waiting period, they should immediately notify Kiln.
• Kiln reserves the right to request an extension of the waiting period in exceptional circumstances, which will be communicated to the researcher in writing.

Previous Audits

Kiln has provided completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.

Proof of Concept (PoC) Requirements

A PoC is required for the following severity levels:

• Smart Contract - Critical
• Smart Contract - High
• Smart Contract - Medium

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.

Other Terms and Information

• This bug bounty program will have a hard cap of USDC 1,500,000. In the event that multiple bug reports are submitted that exceed this amount, the rewards will be provided on a first come first served basis.
• The following roles: Operator, Admin and Proxy Admin are trusted to behave properly and in the best interest of the users. They should not be considered as malicious. Reports taking this assumption will be considered invalid.

KYC Requirement

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:

• 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

KYC information is only required on confirmation of the validity of a bug report.

Primacy of Impact vs Primacy of Rules

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.

Known Issue Assurance

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.

Immunefi Standard Badge

Kiln has satisfied the requirements for the Immunefi Standard Badge, which is given to projects that adhere to best practices.

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 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

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.

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.