Puffer

Puffer is an Ethereum Liquid Restaking Protocol for pufETH

Puffer is an Ethereum service that stakes ETH, meaning it helps secure the network for rewards, and issues a spendable receipt called pufETH. Its native restaking design also assigns validator ETH to EigenLayer services, while pufETH accrues value through a rising, non-rebasing exchange rate.

Bottom line: It is an Ethereum liquid restaking protocol that turns deposited ETH into non-rebasing pufETH, whose exchange rate accrues staking and EigenLayer rewards.

A Liquid ETH Position for Long-Term Treasuries

A long-term ETH holder uses pufETH to retain a transferable asset while the underlying position earns staking rewards.

Consider a treasury that wants Ethereum staking exposure without maintaining validator clients, signing daily messages, or locking every unit behind a withdrawal queue. Depositing through Puffer replaces the operational position with pufETH in the treasury wallet. The token represents a proportional claim on assets managed by PufferVault, including deposited ETH and accrued rewards after penalties. The wallet balance stays available for transfers or supported DeFi uses, while the vault manages allocation into Ethereum validators and native restaking through EigenLayer. It also avoids concentrating that work inside the treasury's own operational controls.

How Do You Enter a pufETH Position?

A user enters a pufETH position by depositing supported Ethereum assets or buying pufETH in a decentralized market.

Direct Minting

The Puffer application accepts ETH, WETH, Lido stETH, and wstETH for direct minting. ETH needs no token approval, so minting requires one staking transaction. stETH and wstETH use a Permit signature before the staking transaction; signing the Permit costs zero gas because it is not an on-chain transaction. WETH instead requires an approval transaction before the deposit. In every route, the interface quotes pufETH from the vault exchange rate before confirmation.

Market Acquisition

Buying on Curve, Uniswap, or Balancer exchanges an existing asset for pufETH rather than minting new vault shares. The market quote includes pool liquidity, swap fees, and price impact, while direct minting follows the protocol conversion rate plus Ethereum gas. A wallet should show Ethereum as the network and enough ETH for transaction fees. Acquiring pufETH does not require the holder to run validator software or own 32 ETH.

The Non-Rebasing pufETH Exchange Rate

The pufETH balance stays fixed as rewards increase the amount of underlying ETH represented by each token, as explained in Using Puffer.

Shares Stay Fixed

The vault treats pufETH as a reward-bearing ERC-20 share modeled around the ERC-4626 tokenized-vault interface. Its accounting uses 18 decimal places, matching the standard Ethereum unit convention where 1 ETH equals 10 18 wei. Rewards raise total assets without issuing the same proportion of new shares. Penalties move the numerator in the opposite direction, so appreciation is an economic outcome rather than a fixed schedule. Wallets therefore show token units separately from the ETH claim behind them.

Worked Exchange-Rate Example

For one worked example, use these hypothetical changing inputs: 12 ETH in total assets, 10 pufETH in supply, a 4 pufETH holder balance, and zero penalties. Dividing 12 by 10 produces an exchange rate of 1.2 ETH per pufETH. Multiplying the holder balance by 1.2 produces a vault claim of 4.8 ETH before withdrawal fees and gas. The wallet still displays 4 pufETH because the token does not rebase.

Redemption Value and Market Price

The vault rate and a decentralized-exchange price answer different questions. The vault rate measures accounting value per share; a pool price reflects immediate buyers, sellers, liquidity, and fees. A temporary discount does not alter the number of pufETH in a wallet. It changes the ETH available from selling through that pool, while the protocol withdrawal path follows its own liquidity and timing rules.

Validator Tickets and the 2 ETH Bond

Validator Tickets separate staker accrual from daily validator performance by selling operating rights to bonded node operators.

Node operators in Puffer post a 2 ETH bond and at least 28 Validator Tickets before receiving 32 ETH for one Ethereum validator. Each Validator Ticket represents one validator-day, and the protocol consumes one ticket per active validator per day. Ticket purchases send ETH into vault accounting before the related validator produces rewards. This front-loading reduces the direct link between one operator's later performance and the reward already credited to pufETH.

The node operator keeps 100% of the validator's consensus and execution rewards during the covered operating period. The bond absorbs inactivity losses and slashing penalties within its value; a slashed operator forfeits the entire bond. Puffer also defines a 22% burst threshold as a self-cap on its share of Ethereum validators. These controls distribute responsibility, yet they do not turn the vault share into principal-protected ETH.

Native Restaking Through EigenLayer Modules

The Puffer module system groups Ethereum validators under EigenPods, then delegates restaking duties to approved operators serving Actively Validated Services.

Validator Layer

Each module controls one EigenPod and receives multiple Puffer validators. A validator carries 32 ETH and points its withdrawal credentials to that EigenPod, allowing native restaking of the validator balance. Puffer node operators continue handling Ethereum consensus duties. Their role remains separate from the restaking operator responsible for additional service work.

AVS Layer

EigenLayer lets restaked validators support Actively Validated Services, commonly shortened to AVSs. Puffer governance selects eligible services and restaking operators for protocol modules. That curation matters because each service defines duties, compensation, and slashing conditions. The module therefore adds a second rule set beside Ethereum proof of stake, rather than merely increasing the base validator reward. Governance can revise both selections through protocol decisions.

Reward Flow

Fees from supported AVSs return through the module structure, with commissions allocated to participating operators and value routed toward pufETH accounting. Validator Ticket proceeds provide another source. Neither component sets a permanent annual percentage yield. The realized rate follows Ethereum issuance, validator participation, execution rewards, ticket pricing, service payments, penalties, and the pufETH supply over the measurement period.

Putting pufETH to Work in DeFi

pufETH remains an ERC-20 asset, so holders transfer it and place it in compatible DeFi contracts.

Supported pools on Curve, Uniswap, and Balancer provide routes between pufETH and other Ethereum assets. Liquidity provision adds pool-specific exposure: a holder receives pool shares, pays gas, and accepts changes in the relative value of the paired assets. ERC-4626-style conversion functions also help contracts estimate shares and underlying assets consistently. Integrations still choose their own oracle, collateral, and withdrawal rules, so Puffer's vault rate does not automatically control every external position.

Composability creates additional uses without changing pufETH itself. A transfer sends the same non-rebasing token to another Ethereum address, and a supported vault can build another strategy around it. Each added contract introduces separate terms and accounting. The holder should distinguish the base pufETH claim from any pool token or vault receipt issued afterward.

What Risks Come With pufETH?

pufETH combines validator, restaking, smart-contract, liquidity, and governance exposures within one exchange-rate-bearing token on Ethereum.

The 2 ETH operator bond provides a defined first-loss buffer for validator-level penalties, but losses exceeding that bond reach pooled accounting. Restaking also places stake under AVS conditions, so Ethereum consensus performance is only one part of the exposure. Audits from BlockSec, SlowMist, Quantstamp, Trail of Bits, Nethermind, and Creed assess specific contract versions; they do not remove execution or upgrade risk. A holder therefore tracks both the pufETH exchange rate and the exit route available for the intended holding period. The bond limits one loss layer, not every protocol dependency.

Orange cartoon fish with white stripes and three rising bubbles
Orange cartoon fish with white stripes and three rising bubbles

Withdrawal Paths, Fees, and Timing

The Puffer withdrawal system offers a one-step WETH route for speed and a two-step route for lower protocol cost.

The one-step route charges 1%, while the two-step route charges no protocol fee and sets a 0.01 pufETH minimum. The one-step route uses liquidity held for immediate settlement and completes in one transaction. The standard route starts with a gas-free Permit signature, then uses one transaction to create the request and another to claim WETH after processing.

Standard processing reaches roughly 14 days when the protocol must exit validators and move funds through EigenLayer withdrawal steps. Each exited validator releases a 32 ETH balance, so large requests can require several validator exits. Available vault liquidity shortens the wait. Ethereum gas remains separate in both modes and follows the network base fee, the selected priority fee, and the gas consumed by each transaction.

Lido, Rocket Pool, Renzo, and Kelp DAO as Alternatives

Lido, Rocket Pool, Renzo, and Kelp DAO expose ETH staking through different operator, token, and restaking designs.

Lido issues rebasing stETH and its non-rebasing wrapper wstETH through a broad operator set. Rocket Pool issues non-rebasing rETH and uses permissionless minipool operators with their own collateral. Both center on Ethereum liquid staking, while a holder seeking restaking adds another protocol or strategy. Their deeper token liquidity and different operator structures change the decision even when the underlying asset remains staked ETH.

Renzo issues ezETH for managed restaking strategies, while Kelp DAO issues rsETH against supported restaked assets. Both bundle EigenLayer exposure into liquid tokens, placing operator selection and AVS allocation behind their respective governance systems. Puffer distinguishes its model through native validator restaking, a 2 ETH node-operator bond, and Validator Tickets that prepay expected daily validator rewards.

The meaningful comparison covers token accounting, withdrawal mechanics, market liquidity, operator access, governance control, and smart-contract layers. A non-rebasing token such as pufETH, rETH, ezETH, or rsETH uses an appreciating claim rather than a growing wallet balance. That shared surface does not make their underlying collateral, reward routing, or penalty allocation interchangeable.

From Liquid Restaking to the Wider Puffer Stack

The wider Puffer stack adds PUFFER governance, vlPUFFER locking, UniFi, and a preconfirmation service beside liquid restaking.

PUFFER is the ecosystem governance token, not the receipt for deposited ETH. Its maximum supply is 1,000,000,000 tokens. Governance covers fees, limits, bond requirements, guardians, restaking operators, and approved AVSs. Locking at least 10 PUFFER creates non-transferable vlPUFFER voting power. One wallet holds one active lock, with terms ranging from 30 days to 2 years and multipliers ranging from 1x to 24x.

After a vlPUFFER lock expires, the owner has a 7-day withdrawal window before another account can kick the position. The kicker receives 1% of the locked PUFFER, and 99% returns to the owner. These governance mechanics do not change the pufETH balance or make PUFFER a claim on PufferVault assets. They govern decisions across the protocol and its broader product family.

UniFi is Puffer's based-rollup project, while Puffer Preconf supplies preconfirmation services through EigenLayer. Those products extend the same Ethereum-focused stack into execution and rollup infrastructure. For a pufETH holder, the essential distinction remains clear: pufETH tracks restaked ETH, while PUFFER governs the ecosystem.

Puffer: reader questions

Can a hardware wallet hold pufETH?

Yes, a hardware wallet can control an Ethereum address holding pufETH. Ledger and Trezor devices keep the signing keys offline, while an interface such as MetaMask or Rabby displays the ERC-20 balance and prepares transactions. The token remains on Ethereum rather than inside the device. If the wallet interface does not list pufETH automatically, adding the verified token contract enables balance display without moving the tokens. The address does not change.

Does minting pufETH create a Puffer account?

No, minting pufETH records an on-chain balance to an Ethereum address rather than creating a username-and-password account. The wallet authorizes the deposit, and PufferVault credits pufETH to the designated recipient. Portfolio interfaces read that public token balance from Ethereum. Access through a custodian or institution follows the provider's separate controls, but the underlying token still belongs to an address. Recovery follows the wallet or custodian process, not a password reset built into Puffer. No separate profile controls the resulting vault shares.

Must a Puffer depositor operate Ethereum validator software?

No, depositing into Puffer does not require validator hardware or client software. The depositor supplies ETH or another supported asset and receives pufETH, while bonded node operators run the Ethereum validators. Operating a node is a separate role with a 2 ETH bond, Validator Tickets, key-management duties, and infrastructure requirements. The depositor still pays Ethereum transaction gas and manages the pufETH token directly in a compatible wallet.

Will an Ethereum multisig accept pufETH?

Yes, an Ethereum multisig can own pufETH because the token follows the ERC-20 transfer model. A Safe account, for instance, can receive the token and approve transactions under its configured signer threshold. Minting, swapping, or withdrawing still requires the multisig interface to support the relevant contract call. Signers should review the quoted asset amount, destination, and transaction sequence because a multisig approval policy does not alter Puffer's vault rules. The Safe signer threshold controls authorization, while Ethereum settles one contract transaction for the account.

Is there a fixed maturity date for pufETH?

No, pufETH has no fixed maturity date because it represents an ongoing share of PufferVault rather than a dated bond. A holder chooses when to transfer, sell, or request withdrawal, subject to the available route and its rules. The exchange rate continues reflecting vault assets, rewards, penalties, and supply while the token remains outstanding. Standard withdrawal timing starts only after the holder submits a request; ownership alone starts no countdown.

Which token pays gas when minting pufETH?

ETH pays the network gas for every Puffer minting transaction on Ethereum. This remains true when the deposited asset is WETH, stETH, or wstETH, because Ethereum validators charge transaction fees in ETH rather than the transferred ERC-20 token. An ETH deposit needs one staking transaction, while WETH also needs an approval transaction. Permit signatures for stETH and wstETH cost no gas, although the following staking transaction still consumes ETH. Gas availability matters before both the approval and final staking transaction enter the network.

Can pufETH be sent to an incompatible smart contract?

Yes, an ERC-20 transfer can deliver pufETH to a contract even when the contract has no function for using or returning it. Ethereum processes the token transfer to the recipient address, and Puffer does not add recovery logic to arbitrary contracts. The sender should use the destination's intended deposit method and confirm it credits the correct account. A compatible vault or pool normally issues its own receipt token.

What records identify a pufETH deposit?

A complete pufETH deposit record includes the Ethereum transaction hash, wallet address, deposited asset, input amount, received pufETH amount, exchange rate, gas paid, and confirmation time. Those fields connect the wallet balance to the original on-chain action and support later accounting. Deposits made with an ERC-20 asset also have approval or Permit context, while a direct ETH deposit does not. Subsequent transfers, pool deposits, and withdrawals create separate records with their own rates and fees. A block explorer can confirm every recorded value independently.