Zest Protocol

Zest Protocol is a Bitcoin lending protocol. Zest Protocol operates on-chain and is open-source.

Zest Protocol exists to make Bitcoin productive. All of it. The protocol strives to create a vibrant borrowing and lending ecosystem around BTC the asset.

For more information about Zest Protocol, please visit https://www.zestprotocol.com/

Zest Protocol provides rewards in USDC/T on Ethereum, denominated in USD.

Maximum Bounty

$100,000

Live Since

11 March 2024

Program Requirements

• PoC Required
• Vault program
• Arbitration enabled

Immunefi Vault Program

Public vault address: 0x52f410595336f15f9C47FA46657D45354FbC5295

Rewards

Zest Protocol provides rewards in USDC, USDT on Ethereum, denominated in USD.

Rewards by Threat Level

Smart Contract

• Critical: Max $100,000 / Min $20,000 (Primacy of Impact)
• High: Max $20,000 / Min $1,000 (Primacy of Impact)

Websites and Applications

• Critical: Max $25,000 / Min $5,000

Critical Reward Calculation

Mainnet assets: Reward amount is 10% of the funds directly affected up to a maximum of $100,000.

Minimum reward to discourage security researchers from withholding a bug report: $20,000

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. This is because the project can mitigate the risk of further exploitation by upgrading or pausing the component where the vulnerability exists. The reward amount will depend on the severity of the impact and the funds at risk.

For critical repeatable attacks on smart contracts that cannot be upgraded or paused, the project will consider the cumulative impact of the repeatable attacks for a reward. This is because the project cannot prevent the attacker from repeatedly exploiting the vulnerability until all funds are drained and/or other irreversible damage is done. Therefore, this warrants a reward equivalent to 10% of funds at risk, capped at the maximum critical reward.

High Level Report Calculation

High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties are rewarded within a range of USD 1,000 to USD 20,000 depending on the funds at risk, 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. This is because as the duration of the freezing lengthens, the potential for greater damage and subsequent reputational harm intensifies. Thus, by increasing the reward proportionally with the frozen duration, the project ensures stronger incentives for bug disclosure of this nature.

Web/Apps Critical Rewards

For critical web/apps bug reports will be rewarded with USD 25,000, only if the impact leads to:

• A loss of funds involving an attack that does not require any user action
• Private key or private key generation leakage leading to unauthorized access to user funds

All other impacts that would be classified as Critical would be rewarded a flat amount of USD 5,000.

Reward Payment Terms

Payouts are handled by the Zest Protocol team directly and are denominated in USD. However, payments are done in USDC/T on Ethereum.

Primacy of Impact vs Primacy of Rules

Zest Protocol adheres to the Primacy of Impact for the following impacts:

• Smart Contract - Critical
• Smart Contract - High
• Websites and Applications - 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.

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.

Proof of Concept (PoC) Requirements

A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules.

Public Disclosure of Known Issues

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.

Any draining of funds via the token authentication use of tx-sender is not in the scope of this bug bounty. Please see the Zest Protocol Borrow Audit (https://coinfabrik.b-cdn.net/wp-content/uploads/2024/02/Zest-Protocol-Borrow-Audit-2024-01.pdf) page 7 for more details.

Previous Audits

Zest Protocol's completed audit reports can be found at https://coinfabrik.b-cdn.net/wp-content/uploads/2024/02/Zest-Protocol-Borrow-Audit-2024-01.pdf. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.

Immunefi Standard Badge

By adhering to Immunefi's best practice recommendations, Zest Protocol has satisfied the requirements for the Immunefi Standard Badge.

Audits

KYC

KYC information is not 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 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:

• Chain Rollbacks
• Pre-Impact Bug Monitoring
• Attack Investment Amount
• Attacks With A Financial Risk To The Attacker
• When Is An Impactful Attack Downgraded To Griefing?