Renzo is a Liquid Restaking Protocol Built Around ezETH

The ezETH Decision Starts With Liquidity and Exit Timing

The ezETH decision turns on whether you want a transferable ETH claim and can accept a queued exit.

Holding ezETH keeps a restaked position usable as an ERC-20 token, so it fits a wallet, a swap route, or a compatible DeFi position. The trade-off is layered exposure: Ethereum validators generate base rewards, EigenLayer extends the stake to Actively Validated Services, and Renzo chooses operators and allocations. A user seeking simple ETH staking gets a narrower mechanism from Lido stETH or Rocket Pool rETH. Someone wanting direct control over EigenLayer delegation gives up the pooled token’s convenience and manages the position separately.

Exit timing settles the choice. Selling ezETH on a decentralized exchange uses available market liquidity and its quoted price. Protocol redemption follows the underlying unstaking and buffer process, while instant withdrawal uses Renzo’s liquidity buffer and charges a variable fee. Those routes exchange certainty about the protocol claim for different combinations of time, price impact, and execution cost.

A First Deposit Takes an EVM Wallet and ETH or stETH

A first Renzo deposit needs an EVM signer, network gas, and either native ETH or supported stETH.

Wallet choice changes key recovery, not ezETH economics. Native ETH skips an ERC-20 allowance, while a first stETH deposit normally requires one approval transaction and one deposit transaction. Keep enough ETH for both Ethereum gas and the later withdrawal claim. The basic deposit sequence stays short:

1. Connect the intended EVM account.
2. Select Ethereum and the deposit asset.
3. Review the quoted ezETH amount.
4. Approve stETH when an allowance is required.
5. Sign the deposit and confirm the ezETH balance.

ezETH Converts Pooled Stake Into a Transferable Claim

Renzo’s ezETH represents a proportional claim on pooled collateral, validator balances, and accrued protocol rewards.

DepositQueue and Validator Creation

Native ETH enters the DepositQueue until the pool assembles 32 ETH, Ethereum’s validator deposit size. The contract then funds a Beacon Chain validator and points its withdrawal credentials toward an EigenPod. Depositors don’t need 32 ETH individually because the pool combines their contributions before validator creation.

RestakeManager and Operator Delegation

The RestakeManager accounts for assets held in contracts, stake delegated through EigenLayer, and validator balances on the Beacon Chain. It distributes pooled stake among active OperatorDelegator contracts using assigned weights chosen for the protocol’s strategy. Operators run Ethereum validators and the software required by selected Actively Validated Services. The receipt token then gives holders one pooled economic claim across those delegated positions.

WithdrawQueue and Token Burning

Minting increases ezETH supply at the current exchange rate. A protocol withdrawal reverses the relationship: the WithdrawQueue locks the requested ezETH, and the protocol burns it when the claim releases collateral. Deposits, rewards, and validator exits first replenish the withdrawal buffer; surplus value returns to the deposit side for compounding, as covered in Using Renzo.

Rewards Accrue Through the ezETH Exchange Rate

ezETH rewards appear when each token represents more underlying ETH, not when the wallet receives extra tokens.

The exchange rate divides Renzo’s ETH-denominated protocol value by total ezETH supply. That value includes collateral in contracts, EigenLayer positions, and Beacon Chain validator balances. Staking and restaking rewards increase the numerator without a matching supply increase, producing Compound-style reward-bearing accounting. Renzo lists a 10% fee on rewards generated through restaking and divides that fee 50/50 between protocol reserves and node operators. Each side therefore receives 5% of the gross restaking reward represented by the fee, while the principal stays outside that calculation. Live APY isn’t fixed; validator performance, AVS payments, penalties, and compounding cadence determine it.

Standard and Instant Withdrawals Trade Time for Cost

The ezETH withdrawal system splits into a queued redemption with a later claim and an instant buffer-funded exit with a fee.

Queued Redemption

A standard ezETH withdrawal can take up to 15 days and ends with a separate claim transaction. The protocol’s withdrawal design includes a 3-day buffer delay, while an available buffer produces an expected wait near 7 days. An empty buffer extends the expected range to 10–15 days because assets must move through EigenLayer and Beacon Chain exit mechanics. Rewards stop accruing on the requested ezETH when the withdrawal starts. After the cooldown, the user signs the claim transaction to receive the selected collateral.

Instant Buffer Exit

Instant withdrawal settles against collateral already held in the buffer, so it avoids the standard queue’s waiting period. Its fee moves between configured minimum and maximum basis-point parameters as buffer fullness changes. A fuller buffer produces the lower end of the range; a withdrawal pushing liquidity below the minimum target reverts. The interface quote therefore matters at confirmation time, because there’s no single fixed instant-exit fee.

Ethereum Mainnet and Layer 2 Deposits Follow Different Paths

The network choice determines whether Renzo stakes assets directly on Ethereum or first moves value through a cross-chain route.

Ethereum mainnet holds the canonical ezETH accounting and supports protocol withdrawals. Native restaking from Arbitrum and Base accepts ETH, WETH, or wstETH through a cross-chain deposit design using Hyperlane and Chainlink components. That route includes a 7-day canonical proof wait behind the pooled settlement process. Renzo batches deposits every 12 hours or once a network reaches 32 ETH, and a verification check runs every hour. These timings describe the bridge’s backend movement; the user receives the layer’s ezETH representation through the deposit flow.

The cross-chain bridge fee is 5 basis points for deposits up to 32 ETH and caps the charged amount at that threshold. One basis point equals 0.01%, so 5 basis points equals 0.05%. Larger deposits therefore face a lower effective percentage after the cap. A separate time-discount component tracks the staking return missed while assets remain in transit.

Layer 2 transaction costs remain separate from Ethereum settlement costs. A later move back to mainnet adds another bridge action before standard redemption.

DeFi Utility Extends Beyond Holding ezETH

ezETH stays useful when a compatible market accepts its ERC-20 accounting and understands its exchange-rate growth.

A holder can keep ezETH, trade it, provide liquidity, or supply it to a lending venue after that venue lists the token. Each use adds a mechanism beyond Renzo. Curve pools concentrate on asset exchange, Balancer pools define their own weights and fee settings, and Pendle separates principal exposure from time-bounded yield exposure. A decentralized-exchange sale settles at the pool’s market price rather than Renzo’s redemption calculation. Liquidity providers also take pool-balance and price-range exposure, while borrowers add collateral ratios, interest, and liquidation thresholds. The token’s portability preserves optionality, but each integration writes its own exit conditions.

The Risk Stack Adds EigenLayer to Ethereum Staking

In day-to-day use, Renzo adds contract, operator, AVS, oracle, and liquidity exposures to the familiar risks of Ethereum staking.

Ethereum and Operator Exposure

A pooled validator still faces Ethereum penalties and slashing. Restaking extends enforceable conditions to the Actively Validated Services selected through EigenLayer. Renzo allocates stake across operators, so ezETH holders accept those delegation decisions rather than selecting an operator for each token. The 32 ETH validator unit also means deposits and exits move through pooled operations.

Contracts, Oracles, and Upgrades

Upgradeable proxy contracts let the system adapt as EigenLayer interfaces change, with upgrade authority controlled through protocol governance and multisignature roles. Layer 2 pricing also relies on Chainlink data and cross-chain messaging. Independent reviews cover different releases and components rather than one permanent configuration. Halborn, Sigma Prime, Code4rena, and Nethermind have each reviewed parts of the contract system, yet an audit remains bounded by its defined code and scope.

Liquidity and Composed Positions

ezETH can trade above or below its protocol exchange rate when pool supply and demand diverge. A swap realizes the market quote; a redemption follows the queue. Lending and leveraged loops add liquidation risk if collateral values move or borrowing costs rise. The most consequential exposure comes from combining restaking with debt, because several independent mechanisms must remain within their limits.

EigenLayer, EtherFi, Puffer, and Lido Set Different Boundaries

Alternatives differ mainly in delegation control, reward accounting, validator design, and whether they include restaking at all.

Direct EigenLayer restaking leaves strategy and operator choices closer to the restaker, and EigenLayer doesn’t issue a fungible token for those positions. EtherFi offers rebasing eETH plus non-rebasing weETH, giving users two accounting formats for native restaking. Puffer Finance issues pufETH as a reward-bearing ERC-20 vault claim tied to native staking and EigenLayer restaking. Lido’s stETH rebases through Ethereum staking rewards but doesn’t itself represent a pooled EigenLayer strategy.

Rocket Pool rETH provides another staking-only exchange-rate token. Renzo’s distinction is pooled strategy management through ezETH, combined with both standard redemption and a buffer-based instant route. The appropriate boundary follows the exposure the user wants to outsource.

REZ Governs Parameters Rather Than Backing ezETH

REZ gives holders governance rights, while ezETH remains the separate claim tied to restaked ETH collateral.

REZ uses 18 decimal places and has a published maximum supply of 10,000,000,000 tokens. Its original allocation schedule assigned 32% to the community, 31.56% to fundraising, 20% to core contributors, 12.44% to the foundation, 2.5% to a launch pool, and 1.5% to liquidity. Governance covers risk frameworks, accepted collateral, concentration limits, operator and AVS whitelists, treasury decisions, and grants. Those votes shape protocol configuration, but REZ price and ezETH’s ETH exchange rate follow different economic inputs.

The Platform Now Spans Three Product Suites

The Renzo platform now organizes three product suites, while ezETH remains its Ethereum-and-EigenLayer liquid restaking product.

The Staking Suite includes receipts tied to different assets and security systems. pzETH connects Ethereum collateral to Symbiotic, while ezSOL and ezJTO use Jito Restaking on Solana. ezREZ and ezEIGEN restake their corresponding ERC-20 assets through EigenLayer. Each token has its own collateral, reward source, fee schedule, and withdrawal rule, so ezETH’s 15-day ceiling shouldn’t be applied across the lineup.

Reserve Vaults package managed onchain strategies, and the Enterprise Suite adds institutional configuration and controls. These products extend Renzo beyond its original liquid-restaking entry point.

For an ETH restaker, the core decision remains narrower: accept pooled operator selection and layered risk in exchange for a portable, reward-bearing ezETH claim.