ReserveStrategy-rateStrategyStableOne (zkSync)

ReserveStrategy-rateStrategyStableTwo (zkSync)

ReserveStrategy-rateStrategyVolatileOne (zkSync)

ReserveStrategy-rateStrategyStableOne (Manta)

ReserveStrategy-rateStrategyStableTwo (Manta)

ReserveStrategy-rateStrategyVolatileOne (Manta)

ZeroLend's deployed contracts can also be found here: https://docs.zerolend.xyz/security/deployed-addresses

ZeroLend’s up to date codebase can be found here https://github.com/zerolend 

The zkSync contracts are the same as the Manta contracts. Where one’s deployed contract isn’t verified, it’s content can be known by referring to the deployment on the other chain, or by checking GitHub.

### Whitehat Educational Resources & Technical Info

Documentation: https://docs.zerolend.xyz/ 

**Is this an upgrade of an existing system? If so, which? And what are the main differences?**

- ZeroLend is a fork of AAVE V3 with changes in the incentive mechanisms that make it very similar to Radiant Capital. The incentive mechanism is located in the governance repo https://github.com/zerolend/governance 

- ZeroLend uses the same EVM as Aave and does not use zk code in itself, but does run on a different compiler which introduces complexity and the potential for novel bugs.



**Where do you suspect there may be bugs?**

- The incentive contracts (https://github.com/zerolend/governance) are custom-made code so this is an area of concern.
- Misconfigurations in the lending market (parameters, oracles, etc).
- Permission issues (like EOAs having admin access) and similar access issues.


**Which part(s) of the system do you want whitehats to attempt to break the most?**

- Everything already live on zkSync and Manta, such as: 
  - Manipulation in terms of asset price
  - Manipulation that creates bad debt
  - Creating any other asset risk in the lending market.
- Any other hack which could bring down the protocol is a major concern.


**Are there any assumed invariants that you want whitehats to attempt to break?**

- All positions should have a health factor > 1.



**What ERC20 / ERC721 / ERC777 / ERC1155 token standards are supported? Which are not?**

- Only ERC20. Nothing else.


**What emergency actions may you want to use as a reason to invalidate or downgrade an otherwise valid bug report?**


- Same emergency actions as Aave; we can freeze the protocol, we can freeze an asset if it becomes more risky. We likely wouldn’t want to invalidate a bug on account of these, and may not downgrade it either. This would be based on the circumstances.



**What Roles are there, and what capacities do they have?**

- Same as aave: https://docs.aave.com/developers/core-contracts/aclmanager
- The ⅔ multisig used is trusted.


**What external dependencies are there?**

- The token assets used.



**What is the test suite setup information?**

- Tests are in Hardhat https://github.com/zerolend/governance/tree/main/test
- To run just do “yarn test.” 


**Public Disclosure of Known Issues**

Bug reports covering previously-discovered bugs (listed below) 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. 


- There is a bug on flashloans, so as a precautionary measure they’re disabled and their bugs are considered out-of-scope: https://governance.aave.com/t/pre-cautionary-measures-on-three-aave-v3-assets/16037 


**Previous Audits**

ZeroLend’s completed audit reports can be found at https://docs.zerolend.xyz/security/audits. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.


### Asset In Scope Policies


**Asset Accuracy Assurance**

Bugs found on assets incorrectly listed in-scope will be considered valid and be rewarded.

**Private Known Issues Reward Policy**

Private known issues, meaning known issues that were not publicly disclosed, are valid, but their rewards are downgraded one severity level.

**Known Issue Assurance**

ZeroLend commits to providing Known Issue Assurance to bug submissions through their program. This means that ZeroLend will either disclose known issues publicly, or at the very least, privately via a self-reported bug submission. 

In a potential scenario of a mediation, this allows for a more objective and streamlined process, in order to prove that an issue is known. Otherwise, assuming the bug report is valid, it would result in the report being considered as in-scope, and due a reward.

**Primacy of Impact vs Primacy of Rules**

ZeroLend adheres to the Primacy of Impact for the following impacts:

- Smart Contract - Critical
- Smart Contract - High


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](https://immunefisupport.zendesk.com/hc/en-us/articles/12340245635089-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.

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.

Trust

stiglitz

MahdiKarimi

offside0011

perseverance

ox7a69

joaovwfreire

EricTee

[banned]

OxSCSamurai

dontonka

Paludo0x

mhmd_alfa

nereus

Lastc0de

azhar0406

Piyushbug

Norah

jimmyhackd

riptide

djxploit

Mirrors

savi0ur

https://drive.google.com/file/d/1ZIp_jHUbIXU1LcJxgHXgWwycrF_dMA9X/view?usp=sharing

ZeroLend is a decentralized lending protocol built on zkSync Era. ZeroLend's core product is its decentralized non-custodial liquidity market. ZeroLend is a fork of AAVE V3 with changes in the incentive mechanisms that make it similar to Radiant Capital.

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

Direct theft of any user NFTs, whether at-rest or in-motion, other than unclaimed royalties

Permanent freezing of funds

Protocol insolvency

Theft of unclaimed yield

Permanent freezing of unclaimed yield

Temporary freezing of funds for at least 1 hour

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

**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](https://immunefisupport.zendesk.com/hc/en-us/articles/9946217628561-Proof-of-Concept-PoC-Guidelines-and-Rules).

**Temporary Freezing of Funds**

If the minimum threshold of temporary freezing for at least 1 hour is not met then the report will be downgraded to Medium severity.

### Miscellaneous Policies

**Responsible Publication**

Whitehats may publish their bug reports after they have been fixed & paid, or closed as invalid, with the following exceptions:


- Bug reports in mediation may not be published until mediation has concluded and the bug report is resolved.

Immunefi may publish bug reports submitted to this boosted bug bounty and a leaderboard of the participants and their earnings.

**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](https://immunefisupport.zendesk.com/hc/en-us/articles/16913132495377-Feasibility-Limitation-Standards) which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.

**Immunefi Standard Badge**

By adhering to Immunefi’s best practice recommendations, ZeroLend has satisfied the requirements for the [Immunefi Standard Badge](https://immunefisupport.zendesk.com/hc/en-us/articles/15006865432209).

The following reward terms are a summary, for the full details read our [Boost Reward Distribution Terms](https://immunefisupport.zendesk.com/hc/en-us/articles/22902062811281-ZeroLend-Boost-Reward-Terms). 

A reward pool of $200,000 USD will be distributed among participants, even if no valid bugs are found. Duplicates and private known issues are valid for a reward.

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.3](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-3/). 

**Reward Payment Terms**

Payouts are handled by the ZeroLend team directly and are denominated in USD. However, payments are done in USDC.

Rewards will be distributed all at once based on Immunefi’s distribution formula after the event has concluded and the final bug reports have been resolved.

NAME	EARNINGS	TOTAL VALID BUGS	INSIGHTS	CRITICAL	HIGH	MEDIUM/LOW
1 Trust	$49,378	9	0	2	6	1
2 stiglitz	$25,416	3	2	1	2	0
3 MahdiKarimi	$24,697	4	0	1	3	0
4 offside0011	$20,671	3	0	1	1	1
5 perseverance	$15,878	5	0	1	2	2
6 ox7a69	$14,360	3	1	0	1	2
7 joaovwfreire	$11,647	3	1	1	1	1
8 EricTee	$8,126	2	0	1	1	0
9 [banned]	$5,998	2	2	0	1	1
10 OxSCSamurai	$4,408	1	1	0	0	1
11 dontonka	$3,439	2	1	0	1	1
12 Paludo0x	$2,795	1	0	0	0	1
13 mhmd_alfa	$2,581	0	4	0	0	0
14 nereus	$2,493	1	1	0	1	0
15 Lastc0de	$1,906	1	1	0	0	1
16 azhar0406	$1,613	0	1	0	0	0
17 Piyushbug	$1,613	0	1	0	0	0
18 Norah	$853	1	0	0	0	1
19 jimmyhackd	$645	0	1	0	0	0
20 riptide	$604	1	0	0	0	1
21 djxploit	$293	1	0	0	0	1
22 Mirrors	$293	1	0	0	0	1
23 savi0ur	$293	1	0	0	0	1

Boost | ZeroLend

Status

Status