Boost | Puffer Finance
Puffer is a decentralized native liquid restaking protocol (nLRP) built on Eigenlayer. It makes native restaking on Eigenlayer more accessible, allowing anyone to run an Ethereum Proof of Stake (PoS) validator while supercharging their rewards.
Status
Immunefi vault program
Rewards by Threat Level
The following reward terms are a summary, for the full details read our Puffer Finance Boost Reward Distribution Terms.
There is a guaranteed reward pool of $50,000.
On top of this there are additional rewards per unique bug found. These rewards are only split among those who find them:
- Additional Rewards per unique Critical bug: $200k
- Additional Rewards per unique High bug: $50k
- Additional Rewards per unique Medium bug: $2k
- Additional Rewards per unique Low bug: $1k
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.
Duplicate Reward Policy
Rewards from the guaranteed rewards pool are distributed evenly among all finders
While additional rewards per unique bug finding are split with 80% going to the chief-finder and 20% being shared equally among all duplicates. The chief-finder is whoever proves the highest severity level of the bug first.
Reward Payment Terms
Payouts are handled by the Puffer Finance 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.
Program Overview
Puffer is a decentralized native liquid restaking protocol (nLRP) built on Eigenlayer. It makes native restaking on Eigenlayer more accessible, allowing anyone to run an Ethereum Proof of Stake (PoS) validator while supercharging their rewards.
The current scope is only to examine the set of smart contracts we have already deployed. These smart contracts allow the depositing of stETH and allow a multisig to sign off on a transaction to deposit the stETH assets to the EigenLayer stETH Strategy smart contract.
For more information about Puffer Finance, please visit https://www.puffer.fi/
KYC not required
No KYC information is required for payout processing.
Proof of Concept
Proof of concept is always required for all severities.
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.