DelegationManager.sol - Transparent Upgradeable Proxy - the current implementation is considered in-scope

StrategyManager.sol - Transparent Upgradeable Proxy - the current implementation is considered in-scope

StrategyBase.sol - Transparent Upgradeable Proxy - the current implementation is considered in-scope

DelayedWithdrawalRouter.sol - Transparent Upgradeable Proxy - the current implementation is considered in-scope

EigenPod.sol - Upgradeable Beacon Proxy - the current implementation is considered in-scope

EigenPodManager.sol - Transparent Upgradeable Proxy - the current implementation is considered in-scope

AVSDirectory.sol - Transparent Upgradeable Proxy - the current implementation is considered in-scope

All code of EigenLayer can be found at [https://github.com/Layr-Labs/eigenlayer-contracts.  ](https://github.com/Layr-Labs/eigenlayer-contracts) Check “releases” to view code from the most recent mainnet deployment.

Most of EigenLayer’s smart contracts are pausable. For any pausable contract, functions which are currently paused are considered out-of-scope, unless an exploit includes a means to bypass pausability.  

Most of EigenLayer’s smart contracts are upgradeable. For any upgradeable contract, the current implementation on ETH mainnet is considered in-scope, while no-longer-used implementations are considered out-of-scope.
Deployed contract addresses on ETH mainnet should be documented in [https://github.com/Layr-Labs/eigenlayer-contracts/#deployments](https://github.com/Layr-Labs/eigenlayer-contracts/#deployments) 

Unless explicitly listed, only pages of the web/app assets in addition to the direct link are considered in-scope of the bug bounty program. Other subdomains are not considered as in-scope. However, for subdomain takeovers that lead to an impact on the in-scope asset, please refer to our page about [Reported Subdomain Takeovers.](https://immunefisupport.zendesk.com/hc/en-us/articles/14352199704593-Reported-Subdomain-Takeovers)

EigenLayer is a protocol built on Ethereum that introduces restaking, a new primitive in cryptoeconomic security. This primitive enables the reuse of ETH on the consensus layer. Users that stake ETH natively or with a liquid staking token (LST) can opt-in to EigenLayer smart contracts to restake their ETH or LST and extend cryptoeconomic security to additional applications on the network to earn additional rewards.

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

Permanent freezing of funds

Retrieve sensitive data/files from a running server such as: /etc/shadow, database passwords, blockchain keys (this does not include non-sensitive environment variables, open source code, or usernames)

Taking down the application/website

Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as: Changing registration information, Commenting, Voting, Making trades, Withdrawals, etc.

Subdomain takeover with already-connected wallet interaction

Direct theft of user funds

Malicious interactions with an already-connected wallet such as: Modifying transaction arguments or parameters, Substituting contract addresses, Submitting malicious transactions

Theft of unclaimed yield

Permanent freezing of unclaimed yield

Injecting/modifying the static content on the target application without Javascript (Persistent) such as: HTML injection without Javascript, Replacing existing text with arbitrary text, Arbitrary file uploads, etc.

Subdomain takeover without already-connected wallet interaction

Smart contract unable to operate due to lack of token funds

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

Injecting/modifying the static content on the target application without Javascript (Reflected) such as: Reflected HTML injection, Loading external site data

Redirecting users to malicious websites (Open Redirect)

Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below. 

__Reward Calculation for Critical Level Reports__

For critical Smart Contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 2,000,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 250,000 is to be rewarded in order to incentivize security researchers against withholding a bug report.   
For Critical website and application bug reports,  the reward amount is 10% of the funds directly affected up to a maximum of USD 100,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 50,000 is to be rewarded in order to incentivize security researchers against withholding a bug report.   

__Repeatable Attack Limitations__

In cases of repeatable attacks for smart contract bugs, only the first attack will be counted, regardless of whether the smart contract is upgradable, pausable, or killable.

__Reward Calculation for High Level Reports__

For High Smart Contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 250,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 50,000 is to be rewarded in order to incentivize security researchers against withholding a bug report. 

__Previous Audits__

EigenLayer has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.

- Any audits listed at https://github.com/Layr-Labs/eigenlayer-contracts/tree/mainnet/audits 
- Any audits listed at https://docs.eigenlayer.xyz/eigenlayer/security/audits 

__Feasibility Limitations__

Bug reports that require an attack that involve one or more other protocols (e.g. utilizing flash loans from a margin protocol or manipulating the spot prices on a DEX), either to make an attack more severe than it would be in isolation, or to achieve an attack that would otherwise be impossible or infeasible, would be out of scope. However, they will be considered as in-scope and categorized according to the program rules as long as all of the following are true:
- Losses or other negative effects of the attack are inflicted upon EigenLayer ecosystem participants 
- The additional protocols used must have enough liquidity in various assets to allow the attack to succeed at the time of bug report submission. For example: if an attack requires an ETH flash loan, but the amount is larger than all the ETH available for loan across the ecosystem

If issues are associated with the pausing functionality of the contract, then the severity will depend on whether the feature was paused or not at the time of the report.

__Proof of Concept (PoC) Requirements__

A PoC is required for the following severity levels:
- Smart Contracts, Critical Severity Level
- Smart Contracts, High Severity Level
- Smart Contracts, Medium Severity Level

All PoCs submitted must comply with the Immunefi-wide [PoC Guidelines and Rules](https://immunefisupport.zendesk.com/hc/en-us/articles/9946217628561-Proof-of-Concept-PoC-Guidelines-and-Rules). Bug report submissions without a PoC when a PoC is required will not be provided with a reward.

__Reward Payment Terms__

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

EigenLayer

Resources & Documentation