21 August 2023
Live since
KYC required
Maximum bounty
09 January 2024
Last updated

Program Overview

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.

For more information about Kiln On-Chain, please visit https://www.kiln.fi/

Kiln provides rewards in USDC. For more details about the payment process, please view the Rewards by Threat Level section further below.

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.

Responsible Publication

Kiln adheres to category 3: Approval Required. This Policy determines what information whitehats are allowed to make public from their submitted bug reports. For more information about the category selected, please refer to our Responsible Publication page.

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 our best practices.

Rewards by Threat Level

Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below.

Reward Calculation for Critical Level Reports

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.

Reward Calculation for High Level Reports

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.

Restrictions on Security Researcher Eligibility

Security researchers who fall under any of the following are ineligible for a reward

  • Any person included on the List of Specially Designated Nationals and Blocked Persons maintained by the US Treasury Department’s Office of Foreign Assets Control (OFAC) or on any list pursuant to European Union (EU) and/or United Kingdom (UK) regulations.

Previous Audits

Kiln has provided these 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.

Reward Payment Terms

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

Smart Contract

USD $100,000 to USD $1,000,000
PoC Required
USD $20,000 to USD $100,000
PoC Required
USD $5,000 to USD $20,000
PoC Required

Assets in scope

All code of Kiln can be found at https://github.com/kilnfi/staking-contracts. Documentation for the assets provided in the table can be found at https://docs.kiln.fi/kiln-on-chain-v1/6eQVsjjelOTzT9cvtG8s/.

Impacts in scope

Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.

Smart Contract

  • Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
  • Permanent freezing of funds
  • Theft of unclaimed yield
  • Direct theft of any commission, whether at-rest or in-motion
  • Permanent freezing of unclaimed yield
  • Temporary freezing of funds
  • Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Out of Scope & Rules

These impacts are out of scope for this bug bounty program.

All Categories

  • Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
  • Impacts caused by attacks requiring access to leaked keys/credentials
  • Impacts caused by attacks requiring access to privileged addresses (governance, strategist) except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible
  • Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
  • Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
  • Best practice recommendations
  • Feature requests
  • Impacts on test files and configuration files unless stated otherwise in the bug bounty program

Smart Contracts and Blockchain/DLT

  • Incorrect data supplied by third party oracles
    • Not to exclude oracle manipulation/flash loan attacks
  • Impacts requiring basic economic and governance attacks (e.g. 51% attack)
  • Lack of liquidity impacts
  • Impacts from Sybil attacks
  • Impacts involving centralization risks
  • Best practice recommendations
  • Triggering withdrawal from a Recipient as long as funds go to the right address
  • Any vulnerability regarding roles and privilege escalation on implementation contracts is out of scope as all deployments are under TUP proxy.

The following activities are prohibited by this bug bounty program:

  • 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