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
Rewards
Rewards by Threat Level
Mainnet assets:
Reward amount is 10% of the funds directly affected up to a maximum of:
$100,000Minimum reward to discourage security researchers from withholding a bug report:
$20,000Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.
Repeatable Attack Limitations
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 [720 blocks] the attack needs for subsequent attacks from the first attack, rounded down
Reward Calculation for High Level Reports
High impacts concerning theft/permanent freezing of unclaimed yield/royalties are rewarded within a range of USD 1 000 to USD 20 000 with the reward calculated based on 100% of the funds at risk, though capped at the maximum high reward.
In the event of temporary freezing, the reward doubles from the full frozen value for every additional 24h that the funds are temporarily frozen, up until a max cap of the high reward
Program Overview
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.
For more information about Zest Protocol, please visit zestprotocol.com.
Zest Protocol provides rewards in USDC/T on Ethereum, denominated in USD. For more details about the payment process, please view the Rewards by Threat Level section further below.
Primacy of Impact vs Primacy of Rules
Zest Protocol V2 adheres to the Primacy of Impact for the following impacts:
- Smart Contract - High
- Smart Contract - Critical
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.
For more information, please see Best Practices: Primacy of Impact
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.
Responsible Publication
Zest Protocol V2 adheres to Category 3: Approval Required. This Policy determines what information researchers are allowed to make public from their submitted bug reports. For more information about the category selected, please refer to our Responsible Publication page.
Audits
KYC not required
No KYC information is required for payout processing.
Proof of Concept
Proof of concept is always required for all severities.
Responsible Publication
Category 3: Approval Required
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.