Renzo Protocol
Bounty Range
Up to $500,000
external program
Renzo Protocol
Renzo is a Liquid Restaking Token (LRT) and Strategy Manager for EigenLayer. It is the interface to the EigenLayer ecosystem securing Actively Validated Services (AVSs) and offering a higher yield than ETH staking. The protocol abstracts all complexity from the end-user and enables easy collaboration between them and EigenLayer node operators.
Renzo strongly advocates for EigenLayer and its goal of facilitating permissionless innovation on Ethereum, and programmatically acquiring trust for the ecosystem. Renzo is built to promote the widespread adoption of Eigenlayer.
The Renzo Protocol is built as an interface to the EigenLayer Protocol smart contracts. As EigenLayer will be upgrading contracts on an ongoing basis, it should be assumed that future releases may cause breaking changes against the existing deployed smart contracts in the Renzo Protocol. Future developments of the Renzo Protocol will be deployed in concert with EigenLayer upgrades, therefore, disclosures relating to potential future vulnerabilities from an upgrade will be out of scope.
For more information about Renzo, please visit https://www.renzoprotocol.com/
Renzo Protocol provides rewards in USDC on Ethereum, denominated in USD.
Smart Contract
Websites and Applications
Mainnet assets: Reward amount is 10% of the funds directly affected up to a maximum of $500,000.
All other impacts classified as Critical: $10,000 flat amount.
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.
For Critical Smart Contract Bugs: The reward amount is 10% of the funds directly affected up to a maximum of USD 500,000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD 100,000 is to be rewarded in order to incentivize security researchers against withholding a critical bug report.
Repeatable Attack Limitations: If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attacks within the first hour 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.
For High Level Reports: High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties are rewarded within a range of USD 10,000 - USD 100,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.
For Critical Web/Apps Bug Reports: Rewarded with USD 25,000, only if the impact leads to:
All other impacts that would be classified as Critical would be rewarded a flat amount of USD 10,000. The rest of the severity levels are paid out according to the Impact in Scope table.
Reward Payment Terms: Payouts are handled by the Renzo team directly and are denominated in USD. However, payments are done in USDC.
The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability.
Renzo will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:
The submission of KYC information is a requirement for payout processing.
Primacy of Impact vs Primacy of Rules: Renzo adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms and conditions stated within this page.
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. Proof of concept is always required for all severities.
Previous Audits: Renzo's completed audit reports can be found at https://github.com/Renzo-Protocol/contracts-public/blob/master/Audit/Renzo_Protocol_EVM_Contracts_Smart_Contract_Security_Assessment.pdf. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
Responsible Publication: Category 3: Approval Required
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.