Renzo (REZ)

Renzo (REZ): The Governance Token Behind a Multi-Network Restaking Platform

Renzo packages restaking into liquid tokens such as ezETH, pzETH, and ezSOL. REZ is primarily the governance asset for deciding how the protocol manages collateral, operators, AVS exposure, treasury funds, and community incentives.

What Renzo does

Renzo is a liquid restaking platform rather than a single staking pool. Its best-known product, ezETH, represents a user’s restaked position in the EigenLayer ecosystem. Users deposit native ETH or supported liquid staking tokens and receive ezETH, which can then be held, traded, or used in DeFi while the underlying position is delegated through Renzo’s strategy-management contracts.

The platform has expanded beyond EigenLayer. pzETH represents a restaked position connected to Symbiotic, while ezSOL represents a restaked position built around Jito and Solana. This gives Renzo a broader product scope, but it also means that the risks and dependencies differ by product rather than being identical across the whole protocol.

How the liquid-token model works

For ezETH, Renzo’s documentation describes a reward-bearing token whose value changes relative to the underlying assets as staking and restaking rewards accrue. The protocol delegates collateral to operators and uses EigenLayer-linked strategies to support Actively Validated Services. Renzo states that staking rewards are passed through and that it charges a 10% fee on restaking rewards, split between protocol reserves and Renzo node operators.

The liquid-token design does not mean instant redemption in every situation. Renzo’s current ezETH documentation says Ethereum withdrawals may take up to 15 days, depending on the restaking strategy and Ethereum validator exit requirements. The pzETH documentation describes a separate withdrawal process that can take 14 to 21 days. These queues are practical constraints for users who need immediate access to collateral.

The role of REZ

REZ is Renzo’s governance token, not the liquid receipt token users receive when depositing ETH, liquid staking tokens, or Solana assets. The project documentation assigns REZ voting use over risk-management frameworks, accepted collateral, concentration limits, operator whitelisting, AVS whitelisting, treasury decisions, and community grants. The Ethereum contract uses 18 decimals and has a stated maximum supply of 10 billion REZ.

The published allocation gives 32% to community purposes, 31.56% to fundraising, 20% to core contributors, 12.44% to the foundation, 2.5% to Binance Launchpool, and 1.5% to liquidity. The same schedule describes cliffs and linear vesting for investor and contributor allocations. Those unlock terms matter because governance influence and market liquidity can change as previously restricted tokens become transferable.

Governance and control

Renzo’s governance documentation describes a process involving discussion, proposal creation, voting, and implementation. The discussion stage is open to community participation through the governance forum. At the initial release of governance, the documentation said that on-chain proposals could be submitted by whitelisted wallets, with a future phase intended to allow any REZ community member to submit proposals. That distinction means token ownership alone should not be assumed to provide unrestricted proposal access.

The governance forum shows that REZ governance has addressed operational and economic questions, including quorum settings, investor-token unlocks, risk reviews, and a proposed buyback-and-burn program. Forum discussion demonstrates that these matters are subject to governance debate; it does not by itself prove that every proposal passed, was executed as described, or created a permanent change to the protocol.

Important dependencies

Renzo’s architecture depends on external restaking systems, node operators, oracle infrastructure, bridges, and the underlying chains. Its L2 documentation identifies EigenLayer-related restaking, Chainlink pricing feeds, and Hyperlane-linked cross-chain infrastructure in the native-restaking design. The project’s contract documentation also lists separate deployment addresses for Renzo contracts, REZ, ezETH, pzETH, ezREZ, withdrawal components, and cross-chain components.

This dependency stack creates several points where outcomes can diverge from the simple description of earning restaking rewards. Operator performance, AVS conditions, oracle pricing, bridge behavior, withdrawal queues, smart-contract upgrades, and liquidity on secondary markets can all affect the usability or market value of a liquid token. Renzo’s public contracts repository provides source code and audit-related directories, but the existence of a public repository is not the same as a guarantee that every deployment is risk-free.

How to read REZ in the Renzo system

For newcomers, the key distinction is between exposure to Renzo’s governance and exposure to a Renzo liquid restaking product. Holding REZ primarily gives governance-related participation described by the project. Holding ezETH, pzETH, or ezSOL represents exposure to separate collateral, operator, restaking, redemption, and liquidity mechanisms. REZ incentives may support product growth, but incentives do not remove the technical and market risks attached to the underlying liquid tokens.

Key takeaways

• Renzo is a liquid restaking platform with products linked to EigenLayer, Symbiotic, Jito, and multiple networks.
• ezETH, pzETH, and ezSOL are product tokens representing restaked positions; REZ is primarily the governance token.
• REZ governance covers collateral, operator and AVS selection, risk frameworks, treasury use, and community grants according to the project’s documentation.
• Maximum supply is stated as 10 billion REZ, with substantial allocations assigned to fundraising, contributors, community programs, and the foundation.
• Redemption periods, external restaking systems, oracle and bridge infrastructure, operator performance, and secondary-market liquidity are material dependencies.

Risks and open questions

• Liquid-token redemption is not always immediate; the project documents withdrawal periods of up to 15 days for ezETH and 14 to 21 days for pzETH.
• Renzo depends on external systems including EigenLayer, Symbiotic, Jito, node operators, oracle feeds, bridges, and the underlying blockchains.
• A liquid restaking token can trade away from the value of its underlying collateral, creating liquidation or liquidity risks for users employing it in DeFi.
• REZ’s governance influence may change as vesting schedules release investor and contributor allocations; the practical concentration of voting power requires ongoing review.
• The public documentation describes governance procedures and proposal categories, but governance outcomes and implementation status must be checked proposal by proposal.
• The project’s public code and documentation do not eliminate smart-contract, upgrade, oracle, bridge, operator, or AVS-specific risks.