Zest Protocol is a Bitcoin lending protocol. Zest Protocol operates on-chain and is open-source. The protocol strives to create a vibrant borrowing and lending ecosystem around BTC the asset.
Zest v2 introduces efficiency groups for granular risk pricing per asset combination, a hub-spoke architecture with market.clar as the central orchestrator, and collateral flexibility letting users choose between isolated (non-rehypothecated) or yield-bearing (rehypothecated) collateral based on their risk preferences.
PoC Required
Vault program
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds
Protocol insolvency
Theft of unclaimed yield
Theft of unclaimed royalties
Permanent freezing of unclaimed yield
Permanent freezing of unclaimed royalties
Temporary freezing of funds
Out of scope
• Any logic related to flashloans.
• Liquidation of disabled collateral or other protocol safety design decisions
• Any "bug" raised that requires an attack vector of DAO compromise, or "accidental" update called to registry by the DAO is out of scope.
• Full control of the asset and egroup registry by the DAO is intended design.
• Invariants that require full knowledge of market and all position state are checked by the DAO off-chain before any egroup updates are approved.
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