Keep3r Network-logo

Keep3r Network

Keep3r Network is a decentralized keeper network for projects that need external devops and for external teams to find keeper jobs.

ETH
Defi
Liquid Staking
Solidity
Maximum Bounty
$250,000
Live Since
19 January 2022
Last Updated
08 April 2024
  • PoC required

Submit a Bug

Rewards by Threat Level

Smart Contract
Critical
Up to USD $250,000
High
Up to USD $40,000
Medium
USD $5,000
Low
USD $1,000

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.

Critical smart contract bug reports must come with a PoC in order to be considered for a reward. Other severity levels may require a PoC during the bug validation process.

Critical smart contract vulnerabilities are paid at 10% of economic damage, primarily based on funds at risk. The team may, at its discretion, take into consideration other aspects such as PR and branding effects. However, there is a minimum reward of USD 50 000.

High smart contract vulnerability rewards are further restricted to be 100% of the funds affected within this severity level. However, the minimum reward is USD 10 000. For vulnerabilities involving a temporary lock-up, the reward is further increased by USD 5 000, until the cap, for every additional 5 minutes, based on the minimum 5 minute requirement to be qualified as in-scope.

Payouts are handled by the Keep3r Network team directly and are denominated in USD. However, payouts are done in ETH.

Program Overview

Keep3r Network is a decentralized keeper network for projects that need external devops and for external teams to find keeper jobs.

A Keeper is the term used to refer to an external person and/or team that executes a job. This can be as simplistic as calling a transaction, or as complex as requiring extensive off-chain logic. The scope of Keep3r network is not to manage these jobs themselves, but to allow contracts to register as jobs for keepers, and keepers to register themselves as available to perform jobs. It is up to the individual keeper to set up their devops and infrastructure and create their own rules based on what transactions they deem profitable.

A Job is the term used to refer to a smart contract that wishes an external entity to perform an action. They would like the action to be performed in "good will" and not have a malicious result. For this reason they register as a job, and keepers can then execute on their contract.

For more information about Keep3r, please visit https://keep3r.network/.

This bug bounty program is focused on their smart contracts and is focused on preventing the loss of funds.

KYC not required

No KYC information is required for payout processing.

Prohibited Activities

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