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.
PoC Required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Deployed Instances. All Timelock, Safe, and RecoverySpell instances deployed through the in-scope factory contracts are also considered in-scope assets. However, vulnerabilities arising from user misconfiguration — such as whitelisting unsafe calldata, failing to configure a guardian, adding an unsafe module, using compromised signing keys, or setting incompatible delay parameters, or setting insecure parameters — are out of scope. See KNOWN_ISSUES.md and EDGECASES.md for documented configuration risks.
https://github.com/solidity-labs-io/kleidi/blob/main/docs/KNOWN_ISSUES.md
https://github.com/solidity-labs-io/kleidi/blob/main/docs/EDGECASES.md
Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original results
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds
Protocol insolvency
Out of scope
Smart Contract specific
- 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
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 (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- 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
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers