Kleidi
Bounty Range
$5,000 - $50,000
external program
Kleidi
The Kleidi Wallet is a collection of smart contracts that can be used to create a full self-custody wallet system for DeFi users. The protocol enables users to access DeFi yields and protocols, pull funds in case of emergency, and recover funds in case of lost keys either through social recovery or predefined backups.
A Timelock module enforces time-delayed execution on all Safe transactions, a Gnosis Guard contract prevents the Safe from bypassing the Timelock, and Recovery Spells enable emergency owner rotation via EIP-712 signatures. Hot signers can execute pre-approved operations immediately through an on-chain calldata whitelisting engine. The system is deployed deterministically via CREATE2, so all contracts share the same addresses across Ethereum, Base, and Optimism. Kleidi Timelocks hold user-deposited ERC-20 tokens and native ETH.
For more information about Kleidi, please visit https://kleidi.io/
Kleidi provides rewards in USDC on Ethereum, denominated in USD.
Smart Contract
| Severity | Reward |
|---|---|
| Critical | Max: $50,000 / Min: $5,000 |
For critical smart contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 50,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 5,000 is to be rewarded in order to incentivize security researchers against withholding a critical bug report.
If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attack will be considered for a reward.
The amount of funds at risk will be calculated with the impact of the first attack being at 100% and then a reduction of 25% from the amount of the first attack for every 300 blocks the attack needs for subsequent attacks from the first attack, rounded down.
Payouts are handled by the Kleidi 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.
Kleidi adheres to Category 2: Notice Required. This Policy determines what information researchers are allowed to make public from their submitted bug reports.
Kleidi adheres to the Primacy of Impact for the following impacts:
Primacy of Impact means that the impact is prioritized rather than a specific asset. This encourages security researchers to report on all bugs with an in-scope impact, even if the affected assets are not in scope.
When submitting a report on Immunefi's dashboard, the security researcher should select the Primacy of Impact asset placeholder. If the team behind this project has multiple programs, those other programs are not covered under Primacy of Impact for this program. Instead, check if those other projects have a bug bounty program on Immunefi.
If the project has any testnet and/or mock files, those will not be covered under Primacy of Impact.
All other impacts are considered under the Primacy of Rules, which means that they are bound by the terms and conditions set within this program.
A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules.
Bug reports covering previously-discovered bugs are not eligible for a reward within this program. This includes known issues that the project is aware of but has consciously decided not to "fix", necessary code changes, or any implemented operational mitigating procedures that can lessen potential risk.
Known issues are documented at:
Kleidi's completed audit reports can be found at https://github.com/solidity-labs-io/kleidi/tree/main/audit. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
The submission of KYC information is a requirement for payout processing.
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. 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.
Researchers should refer to Immunefi's standards on: