bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 14쪽 중 2쪽
ns to
RestakingOperator
contracts, and managing operators' AVS commitments.
For example, adding a new module to the PufferProtocol contract requires governance to:
Vet and select the
restaking operator
to operate on behalf of a RestakingOperator contract.
Vet and
select the Eigenlayer AVSs
that the RestakingOperator contract can opt in to.
Delegate the module's ETH to the RestakingOperator contract.
1️⃣ Staking ETH
Stakers can deposit ETH and mint the
pufETH nLRT
via the PufferVault contract, which serves as a redeemable receipt for their restaked ETH. If sufficient exit liquidity is available, stakers can reclaim their ETH from the PufferVault. Over time, the redeemable amount is expected to increase from
validator tickets
and restaking rewards.
In
contrast with conventional liquid staking tokens (LSTs)
, pufETH can provide strictly more rewards for its holders. Not only does pufETH encompass PoS rewards
and
restaking rewards, but its value can accelerate quickly due to validator ticket sales. Furthermore, the PoS rewards for stakers are decoupled from the protocol validators' performance.
2️⃣ Registering a NoOp Validator
To register a new validator, NoOps deposit
validator tickets
and
2 ETH
as collateral to the PufferProtocol contract. In return, the protocol mints pufETH, which remains locked until it's confirmed that their validator has successfully exited. Locking pufETH serves to:
Align NoOp incentives
Safeguard staker ETH
Increase NoOp profit margins
To ensure the safety of stakers, NoOps must distribute their encrypted validator keyshares to the Guardians'
enclaves
, allowing them to eject the NoOps if their validator balance falls too low or they run out of validator tickets. This requirement is to protect stakers and it will be
upgraded to a trustless solution
once Ethereum's protocol allows it via
EIP-7002
.
3️⃣ Provisioning ETH
Each RestakingModule contract will contain a queue of pending NoOp registrations. As the PufferVault accrues 32 ETH chunks from deposits and rewards, the Guardians will provision the chunks to the NoOps' pending validators, following a round-robin schedule to ensure all of the protocol's modules are serviced.
The provisioning step will create a new validator within the EigenPod whose ETH can be natively restaked on Eigenlayer to serve as collateral for its registered AVS. For this reason, the NoOp's validator's
withdrawal credential
is required to the module's EigenPod contract. After provisioning, the NoOp's validator will have deposited 32 ETH to the
BeaconDepositContract
and will await activation.
4️⃣ PoS Rewards
Once their validator activates, the NoOp is eligible to validate for as many days as the validator tickets they have deposited. Throughout this duration, the NoOp keeps 100% of the generated PoS rewards. Their
execution rewards
are immediately deposited to their wallets, while their
consensus rewards
accrue in the module's EigenPod and can be withdrawn following the NoOp withdrawal process.
Since NoOps receive 100% of the PoS rewards they generate, they are
incentivized
to maximize their validator performance, helping protect staker ETH.
5️⃣ Restaking Rewards
Restaking operators execute the AVSs on the module's behalf and receive a commission for their services. The accumulated fees from these AVSs enhance the value of pufETH. This mechanism allows stakers to achieve higher returns compared to conventional LSTs.
By participating in a restaking module, NoOps bear additional risks to their collateral. To compensate, they are granted a portion of the restaking rewards. This arrangement allows them to earn more rewards than through PoS alone, without the need for additional hardware or computational resources. They can access these rewards periodically, using the same NoOp withdrawal process as for consensus rewards.
️6️⃣ Exiting Validators
When a NoOp wishes to exit the protocol, they must first ensure their associated validator has exited the beacon chain. Once they present verifiable proof of their validator's exit, the contract tallies any penalties related to inactivity or slashing that the validator might have incurred. The corresponding pufETH amount, equivalent to the ETH penalties, is burned from the NoOp's locked collateral and the remainder is returned to the NoOp. This process ensures that stakers are appropriately compensated for any potential ETH losses that might have occurred during the validator lifecycle. Additionally, any unused validator tickets will be returned to the NoOp.
Puffer Walkthrough 👩🏫
0️⃣ Creating PufferModules
1️⃣ Staking ETH
2️⃣ Registering a NoOp Validator
3️⃣ Provisioning ETH
4️⃣ PoS Rewards
5️⃣ Restaking Rewards
️6️⃣ Exiting Validators
## /yield/nodes/requirements
On this page
Anyone can become a Puffer NoOp because our protocol is permissionless!
Becoming a Puffer NoOp requires running a validator. NoOps must lock a refundable pufETH bond, and lock validator tickets which are burned each day of operating a validator, in order to be 32 ETH provisioned to run a validator.
Bond and Validator Tickets
The bond is required as slashing and inactivity insurance. The locked validator tickets act as an incentive alignment. The amount of validator tickets locked determines the length of time the NoOp is entitled to run the validator. Read more about validator tickets
here
. The ETH bond will eventually be converted into pufETH, so NoOps can alternatively deposit their bond as pufETH. In either case, if the validator exits the beacon chain with at least 32 ETH, and was not slashed, the NoOp will receive the entirety of their bond back. If the validator was not slashed, but its balance is less than 32 ETH, the difference will come out of the NoOps bond.
warning
If a validator is slashed, the NoOp will forfeit their entire bond.
NoOp Requirements Summary
2 ETH Bond
At least 28 Validator Tickets
Restaking Module choice
Validator
Validator Requirements
CPU: Quad-core (or dual-core hyperthreaded) CPU
Memory: >= 16GB RAM
Storage: 2 TB SSD (NVMe SSD recommended) for full node
To run a full archive node, over 13.5 TB is needed
Note: As the Ethereum blockchain grows, about 14GB additional storage is needed per week
Bandwidth: >= 25 Mbps download speed
For more information, please see
Geth hardware requirements
Disclaimers
EigenLayer Partial Withdrawals Proofs are being improved 🚧
Currently it is
cost-prohibitive
to withdraw consensus rewards from EigenPods but the EigenLayer team is working to decrease these costs. Until then, withdrawing consensus rewards is temporarily disabled.
NoOp Requirements Summary
Validator Requirements
Disclaimers
## /yield/stakers/stake
On this page
This section will guide you through the process of staking to the Puffer Protocol. Review the
native Liquid Restaking Tokens
section to understand the benefits of staking to the Puffer Protocol.
Basically, when you stake your funds to the Puffer Protocol, you will receive a native Liquid Restaking Token (pufETH) in return. This pufETH will be minted to your wallet and will represent your staked ETH. The pufETH is expected to increase its value overtime.
Connect Wallet
In order to stake to the Puffer Protocol you need to go to the
Stake page
and connect your wallet.
Select asset
The Puffer Protocol app currently supports the following assets:
ETH
: The native token of the Ethereum blockchain.
stETH
: A liquid staking token for Ethereum that represents the staked version of ETH in the Lido protocol. It is pegged 1:1 with ETH.
wstETH
: A wrapped version of stETH. It is not 1:1 with stETH.
WETH
: A wrapped version of ETH. It is 1:1 with ETH.
Select amount
You can select the amount of ETH, stETH, wstETH, or WETH you want to stake. The app will automatically calculate the amount of pufETH you will receive in return. The exchange rate will be the same for ETH, WETH and stETH since they are pegged 1:1. For wstETH, the exchange rate will be different.
To understand the exchange rate, check out the
docs
.
Stake
Once you have selected the amount you want to stake, you can click on the "Stake" button.
In the case of stETH and wstETH, you will need to first sign a Permit in order to allow the Puffer Protocol to spend your stETH/wstETH. Please note that the Permit is a signature and not a transaction, so you will not be charged any gas fees for it.
In the case of ETH, no Permit is needed since ETH is a native token on the Ethereum blockchain.
If you are staking WETH, you will need to sign a transaction to approve the Puffer Protocol to spend your WETH.
In any case, you will need to sign a transaction to stake your funds and receive your pufETH.
Connect Wallet
Select asset
Select amount
Stake
## /yield/deployments/deployed-contracts
On this page
Puffer Protocol Contracts
Puffer's smart contracts are located in two repos:
PufferFinance/pufETH
This repo contains the
PufferVault
contract which is where the protocol's assets (ETH, wETH, stETH) are held and the
pufETH
LRT is minted.
Visit the
technical documentation
for more information.
PufferFinance/PufferPool
This repo contains the core contracts for Puffer's protocol. The core functionality is to:
allow for users to permissionlessly run Ethereum validators
interface with EigenLayer's contracts to enable native restaking and delegation
Visit the
technical documentation
for more information.
Deployment Addresses
Please check
Deployments and Access Control
Github repository for the definitive addresses of all deployed contracts on all chains.
Puffer Protocol Contracts
PufferFinance/pufETH
PufferFinance/PufferPool
Deployment Addresses
## /yield/governance/mission
On this page
Our Vision
At Puffer, we envision a decentralized financial ecosystem that empowers users, fosters innovation, and upholds Ethereum's core principles. Puffer has always striven to preserve what we believe to be Ethereum's most important value - decentralization. This is why our ecosystem has been about fostering permissionless validator operations.
To embody these principles of decentralization within our own protocol, we're transitioning to a Decentralized Autonomous Organization (DAO). This move ensures that the future of Puffer is shaped not by a centralized authority, but by our community of token holders and ecosystem participants. Through the DAO, we're not just advocating for decentralization – we're living it, allowing our governance to reflect the very values we seek to promote in the broader Ethereum ecosystem.
Our Ecosystem
The Puffer ecosystem now encompasses:
Puffer LRT
: Our flagship Liquid Restaking Protocol
Puffer UniFi
: Our Based Rollup stack
Puffer Preconf
: The first-of-its-kind preconf service for based rollup preconfirmations
Our Commitment
Throughout our growth, we remain steadfast in our commitment to building Puffer into a:
Trustless protocol
Decentralized infrastructure
Community-governed ecosystem
The Puffer Foundation
To ensure our growth aligns with our community's vision, we established the Puffer Foundation. Its mandate is to:
Provide initial guidance
Facilitate transparent governance
Support the transition to full community control
Community Governance
The
PUFFER token
is the cornerstone of our governance model, empowering our community to:
Participate in key decisions
Shape the future of the Puffer ecosystem
Uphold Ethereum's core principles in all our endeavors
Inclusive Participation
We believe in the power of diverse perspectives. Therefore:
We invite everyone interested in Puffer's mission to join the conversation and contribute ideas.
While voting rights are reserved for $PUFFER token holders who have locked their tokens in our voting token vlPUFFER, we value input from our entire community.
Your voice matters in shaping our protocol and contributing to the broader Ethereum ecosystem, regardless of token ownership.
Together, we're not just building protocols; we're shaping the future of decentralized finance on Ethereum.
Our Vision
Our Ecosystem
Our Commitment
The Puffer Foundation
Community Governance
Inclusive Participation
## /yield/campaigns/season-1
On this page
Puffer’s Season 1 demonstrated our commitment to Ethereum’s decentralization and user empowerment. This inaugural campaign preceded our TGE, anchored by the Crunchy Carrot Quest, distributed rewards to bolster decentralization, enhance protocol collaboration, and onboard more participants to the Ethereum ecosystem through Puffer.
Crunchy Carrot Quest
The Crunchy Carrot Quest was our flagship incentive campaign in Season 1. By distributing Puffer Points across a carefully curated set of protocol partners, we encouraged activity in key areas of Ethereum’s infrastructure while rewarding meaningful contributions to decentralization. Participants could earn points through activities like restaking via EigenLayer, liquidity provisioning and engaging with partner protocols.
We announced that 7.5% of $PUFFER tokens are to be allocated to the Crunchy Carrot Quest participants, available immediately to reward early Puffer supporters. 50% is available on day 1 and for larger depositors, the rest is vested over 6 months for equal opportunity for all of our community. For more information, refer to the
PUFFER tokenomics
article.
Claims will end on Janaury 14, 2025. If you have not yet made your claims, please do so at the official
Puffer Claims
page.
Partner Collaboration
Season 1 worked with a diverse range of DeFi protocols, creating synergies that benefited the broader Ethereum network. Some highlights included:
Boosting decentralization: By incentivizing staking outside of dominant pools, we successfully reduced stETH’s market dominance by 2.38%, strengthening Ethereum’s network resilience.
Cross-protocol engagement: Participants earned rewards by providing liquidity, participating in governance, or integrating with partner protocols, driving the decentralization of Ethereum.
Point Distribution Framework
Puffer Points were distributed dynamically across partner protocols based on their contributions to network decentralization and user activity. This structure ensured rewards aligned with ecosystem priorities while giving participants a diverse set of opportunities to earn with the Puffer ecosystem.
Empowering Validators at Scale
Season 1 wasn’t just about distributing points; it was about redefining who could participate in Ethereum’s infrastructure. Puffer’s Validator Tickets initiative lowered bond requirements to just 2 ETH, enabling more individuals to become validators and dramatically expanding Ethereum’s decentralization. Over 9,000 validators joined our network through this campaign, marking a significant milestone in Ethereum’s history.
Crunchy Carrot Quest
Partner Collaboration
Point Distribution Framework
Empowering Validators at Scale
## /yield/reference/glossary
On this page
Glossary
Eigenlayer
An Ethereum-based protocol that enables restaking
AVS
Actively Validated Service ~ the term for a service on Eigenlayer
Restaking
Where people reuse collateral to operate ≥ 1 AVS. If this collateral is beacon chain ETH, they are a called a
native restaker
LSP
Liquid Staking Protocol
nLRP
Native Liquid Restaking Protocol. The Puffer protocol offers native ETH liquid restaking on Eigenlayer
pufETH
The yield bearing token that represents staked ETH in Puffer’s LSP
Stakers
The users who “stake” ETH to the vault to receive pufETH
NoOps
The Puffer nodes that operate an Ethereum validator (and optionally additional AVSs)
Guardians
A committee of Ethereum aligned community members and organizations to assist the protocol as it matures
Enclave
A secure-computing environment capable of running Puffer’s anti-slashing technology
Burst Threshold
Code in our smart contracts that self-caps the vault at 22% marketshare
Beacon Chain
The main component of the Ethereum blockchain responsible for Proof of Stake consensus
Beacon Chain Deposit Contract
The smart contract to which a NoOp must deposit 32 ETH to initiate running a validator node
VEM
Voluntary Exit Message ~ a validator-signed message that will exit the signer when broadcasted to the beacon chain
Withdrawal Credentials
A validator parameter that sets where their consensus rewards and full withdrawal eth are sent. For 0x01 (post-Shapella) withdrawals, the credentials are formatted as
0x01000000000000
++
20 byte ethereum address
Consensus Rewards
AKA partial withdrawals or skimmed rewards. These rewards are generated by Ethereum validators performing their PoS duties
Execution Rewards
The rewards earned by a validator when proposing a block. The rewards are composed of priority fees and MEV: Maximal Extractable Value". This refers to the maximum value that can be extracted from block production in excess of the standard block reward and gas fees by including, excluding, and changing the order of transactions in a block.
source
Full Withdrawal
The validator’s entire balance that is withdrawn from the beacon chain to the Ethereum address set by the withdrawal credentials
Slashing
Slashing may refer to a loss of funds triggered by either of the following:
Misbehavior of validator nodes, such as signing two different blocks for the same beacon slot (AKA double-signing).
A Restaking Operator (ReOp) not fulfilling obligations defined by an AVS
Validator Ticket
An ERC20 token. Each Validator Ticket allows operating a validator on the Puffer Protocol for one day.
Bond
An amount of pufETH a NoOp must lend to the protocol during the time of running their validator node. They may lose some or all of this bond if they misbehave or are slashed. NoOps may retrieve this bond after proving they have exited their validator node from the beacon chain
Puffer Module
A contract that defines a set of AVSs which NoOps opting into the module will delegate their ETH funds to running. These NoOps will receive corresponding rewards in return by participating in this Puffer Module
Restaking Operator
AKA ReOp: A NoOp that is delegated funds to operate an AVS on behalf of other NoOps, as part of a Puffer Module
Proof of Rewards
This refers to the process by which NoOps prove and receive the rewards generated as a result of running their validator node
Glossary
Eigenlayer
AVS
Restaking
LSP
nLRP
pufETH
Stakers
NoOps
Guardians
Enclave
Burst Threshold
Beacon Chain
Beacon Chain Deposit Contract
VEM
Withdrawal Credentials
Consensus Rewards
Execution Rewards
Full Withdrawal
Slashing
Validator Ticket
Bond
Puffer Module
Restaking Operator
Proof of Rewards
## /yield/protocol/puffer-modules
On this page
info
Puffer allows Validators to get native restaking exposure to earn more than they could in traditional liquid staking protocols or solo staking.
Native restaking 🥩
A
native restaker
is an Ethereum PoS validator that restakes their 32 ETH to operate EigenLayer
AVSs
. Native restakers are awarded AVS fees in exchange for their service, but are subject to penalties if they break the AVS's rules. To engage in native restaking, validators must point their
withdrawal credentials
to an
EigenPod
contract which then opts-in to restaking and chooses its AVSs.
Native restaking allows validators to better utilize their ETH capital and hardware to supplement their PoS rewards. However, the 32 ETH requirement is too high a barrier for most to participate. Additionally, some AVSs may require far greater computational requirements than what is expected from PoS. Puffer aims to address this through its PufferModules.
Puffer Modules 🐡
At its core, the Puffer protocol is a collection of
PufferModule
contracts. Each module controls an EigenPod that functions as a single native restaker but is composed of
many
NoOp-controlled validators.
Modules are프로젝트로 돌아가기