Series: Hub | Institutional Staking
The Institutional Staking Hub is P2P.org's definitive reference for institutions building proof-of-stake programs. From foundational concepts to infrastructure selection and risk architecture, each article addresses a specific operational or technical dimension that determines how a staking program performs in practice.
Previously in the series: Liquid Staking for Institutions: A Complete Guide for Funds, Custodians, and Treasury Team
What this article covers:
The core argument: Restaking extends the utility of staked capital by allowing it to simultaneously secure additional protocols beyond the base layer. For institutions, that extension introduces stacked slashing exposure, AVS-level smart contract risk, and operator concentration risk that must be explicitly assessed before any restaking program is designed. Restaking is not a yield enhancement on top of staking. It is a structurally different risk commitment.
Restaking for institutions has moved from an experimental DeFi primitive to a multi-billion dollar infrastructure category in under two years. Restaking protocols reached approximately $18 billion in TVL in 2025, peaking above $20 billion, with institutional flows into restaking strategies increasing alongside regulatory clarity and the yield differential compared with traditional finance. Source: Stakin
The regulatory environment is developing but restaking sits outside the scope of the March 2026 SEC and CFTC joint interpretation, which explicitly excluded restaking from its covered protocol staking activities. Institutions engaged in restaking should treat their programs as operating in a legally uncertain environment and consult counsel on both securities law and CEA implications. Source: Gibson Dunn
For custodians, funds, ETF issuers, and treasury teams, the question is now operational: what is restaking exactly, how do actively validated services work, what are the risk categories that are distinct from native and liquid staking, and what does a compliant, institutional-grade restaking program actually require?
This article answers those questions from the ground up.
In native staking, capital secures a single proof-of-stake network. Staked ETH secures Ethereum. That is its one function. When an institution stakes ETH, it earns the protocol-generated rewards the Ethereum network distributes to validators and delegators. The staked capital does one job.
Restaking changes that architecture. It allows staked ETH, or liquid staking tokens representing staked ETH, to simultaneously secure additional services built on top of or alongside the base layer. Traditional proof-of-stake staking secures a single network. Restaking extends that security to additional services without requiring new validator sets or fresh capital. Stakers opt in to securing external services and earn additional protocol-generated rewards on top of their base staking rewards, in exchange for accepting additional slashing risk.
Those external services are called Actively Validated Services, or AVSs. An AVS is any system that needs distributed validation or security: oracle networks, data availability layers, cross-chain bridges, sequencers, and verification services. Each AVS defines its own slashing conditions, its own reward structure, and its own operational requirements for the operators securing it.
For institutions, restaking is not a passive add-on to an existing staking program. It is a decision to extend capital commitment across multiple slashing surfaces simultaneously, in exchange for additional protocol-generated rewards from each AVS the institution opts into. The risk and reward profile changes materially with each additional AVS.
Understanding AVSs is the prerequisite for evaluating any restaking program. An AVS is a service that uses restaked capital as its economic security layer instead of bootstrapping its own validator set from scratch.

AVSs are the demand side of EigenLayer's security marketplace. An AVS can be a data availability layer, oracle network, bridge, decentralized sequencer, AI verification system, off-chain compute service, or any system that needs distributed validation. Each AVS defines conditions under which an operator's stake can be slashed. If an operator fails to meet those conditions correctly, the AVS can initiate a slashing event against the staked capital backing that operator. Source: DL News
The institutional implication is that every AVS an institution opts into is an independent slashing surface. Securing one AVS adds one set of slashing conditions on top of the base Ethereum staking slashing conditions. Securing five AVSs adds five independent slashing surfaces, each with its own operational requirements and governance frameworks.
EigenLayer mitigates correlated slashing exposure with isolated stake allocation, while Symbiotic uses per-vault slashing boundaries to limit how much stake is exposed to any single service. These mechanisms reduce but do not eliminate the compounding slashing exposure that AVS diversification creates.
For institutional due diligence, each AVS must be evaluated independently: its audit history, its slashing conditions, its governance, its revenue model, and the track record of the operators securing it.
Protocol-generated rewards in a restaking program come from two independent sources. The first is the base layer staking reward: the Ethereum network's protocol-defined reward for validator participation in consensus. The second is the AVS reward: the rewards each AVS distributes to operators and restakers for securing its service.
The basic restaking reward stack in 2026 looks like this: 3 to 4% from base Ethereum staking, 1 to 2% from EigenLayer AVS rewards, and a variable amount of points or token rewards on top. Total rewards typically land in the 4% to 7% range when paid in protocol-generated rewards, higher when speculative token incentives are included.
The composition of AVS rewards matters for institutional programs. Rewards denominated in the AVS's own token introduce token price risk and liquidity risk that do not exist in ETH-denominated base staking rewards. Institutions must assess whether AVS reward streams can be received, accounted for, and reported under their applicable accounting and compliance frameworks.
At present, most restaking infrastructure relies on token incentives rather than distributing actual sustainable protocol-generated yield. Analysts predict that, in the future, strategic AVS selection and active portfolio management will play a central role in optimizing reward outcomes for restaked capital. Source: NFT Plazas
Network conditions determine protocol-generated rewards and are variable. P2P.org does not control or set reward rates for base staking or AVS participation.
Restaking introduces a risk profile that is structurally more complex than native or liquid staking. Each category requires explicit assessment before any institutional restaking program is designed.
Native staking carries one set of slashing conditions: the Ethereum protocol rules governing validator behavior. Restaking adds the slashing conditions of every AVS the institution opts into. One of the most pressing issues for institutional participants is the risk of slashing when assets are delegated across multiple networks simultaneously. Each AVS comes with its own risk profile, and the compounding effect of minor risks across multiple services can result in significant losses for institutional portfolios. The absence of a standardized slashing recovery mechanism further complicates risk management. NFT Plazas
Slashing events triggered by AVS-level failures can result in permanent loss of a portion of the restaked capital. Institutions must assess the slashing conditions of each AVS in their approved list and model correlated slashing scenarios across their full restaking program.
In most restaking architectures, institutions delegate to operators who run the node software required by each AVS. Operator selection determines uptime, rule compliance, and slashing exposure. Delegating to a single operator concentrates risk: that operator could suffer downtime, slashing, insolvency, or regulatory pressure. The same logic that applies at the network level in native staking applies at the operator level in restaking programs if an institution fails to diversify across operators. Source: Precedence Research
Institutional restaking programs require operator due diligence that mirrors the validator infrastructure evaluation framework for native staking, applied independently to each AVS the institution participates in.
Restaking protocols operate on smart contracts that govern stake allocation, slashing enforcement, and reward distribution. A vulnerability in those contracts can result in loss of capital that is independent of any slashing event. Unique Stake Allocation in EigenLayer isolates slashable stake so the same chunk of capital is not freely exposed to every AVS at once, which helps limit correlated smart contract exposure across the restaking program. However, smart contract risk cannot be eliminated through protocol design alone. RPC Fast
Most AVSs currently distribute rewards through token incentive programs rather than sustainable fee revenue. The restaking model's core value proposition faces structural headwinds as AVSs struggle to generate sustainable fee revenue. Without meaningful cash flows from secured applications, restaking protocols rely heavily on token emissions, creating inflationary pressure that sophisticated institutions must factor into their reward accounting. Institutions must assess the revenue sustainability of each AVS before committing capital to securing it. Source: P2P.org
Restaked capital is subject to unbonding periods at the base layer and, in some architectures, additional lock-up conditions imposed by individual AVSs. The liquidity profile of a restaking program is more complex than native staking and must be explicitly mapped against the institution's redemption obligations and treasury mandates.
The March 2026 SEC and CFTC joint interpretation explicitly excluded restaking from its covered protocol staking activities. Restaking remains legally uncertain at the federal level. AVS reward tokens carry additional classification questions that remain unresolved. Institutions must assess the treatment of each reward token type under their applicable accounting standards and regulatory framework, and consult counsel before deploying capital. Source: Cahill Gordon
Liquid restaking tokens, or LRTs, extend the same capital efficiency logic that liquid staking tokens introduced to native staking. When an institution restakes ETH or an LST through a liquid restaking protocol, it receives an LRT representing the restaked position. The LRT accrues the rewards of the restaking program and remains transferable and composable.
LRTs represent a claim on restaked ETH plus accrued rewards, while remaining tradable assets. By combining base staking rewards and AVS reward streams with continued liquidity, liquid restaking tokens allow capital to remain deployable while the underlying position secures multiple protocols simultaneously.
For institutions, LRTs introduce all of the risk categories that apply to liquid staking tokens: smart contract risk at the LRT protocol layer, depeg risk in secondary markets under stress conditions, and custody and accounting complexity. Those risks compound with the AVS-level slashing and smart contract risks that restaking itself introduces. The cumulative risk stack of an LRT position is materially more complex than either native staking or liquid staking alone.
In April 2026, Kelp suffered a $292 million exploit that triggered approximately $5.4 billion in withdrawals across the restaking sector. The protocol survived, but the incident reset the risk conversation around the entire liquid restaking token category. This is the risk category that institutions must model carefully before deploying capital into LRT positions.
Operator selection is one of the most consequential decisions in any institutional restaking program. The operator runs the node software required by each AVS, manages the signing infrastructure, and maintains the uptime standards that determine both reward outcomes and slashing exposure.
When a user restakes, they delegate to an operator who will run the required software for each AVS. The restaker accepts that their stake can be penalized not only for Ethereum-level misconduct, but also if the operator fails to perform correctly for any of the services they choose to secure. Poor performance in one attached service can result in loss on the original stake. Source: Precedence Research
For institutions, operator evaluation must cover infrastructure architecture, client diversity, key management practices, AVS selection history, slashing record, governance participation policies, and independent certification. These are the same dimensions that apply to native staking validator selection, extended to cover every AVS the operator secures.
No major slashing event has occurred across any restaking protocol as of mid-2026, but the mechanisms remain largely untested at scale. That absence of historical slashing events should not be treated as evidence of low risk. It reflects the relative youth of the category, not structural safety. Institutional programs must be designed for the slashing scenario, not against the historical average.
P2P.org supports EigenLayer restaking through non-custodial operator infrastructure, with the same validator-level reporting and operational safeguards that apply to our native staking programs. Client assets remain under the institution's control throughout. Explore our EigenLayer restaking infrastructure at p2p.org/networks/ethereum.
Restaking sits at the intersection of staking infrastructure and DeFi participation. It is not a replacement for native staking. It is an extension that institutions evaluate after establishing a sound native staking foundation.
Over $58 billion in capital flows through liquid staking protocols, and an additional $18 billion has moved into restaking as of early 2026, according to DefiLlama. In Europe, several ETPs have launched that stake underlying Ethereum holdings to generate protocol-generated rewards for fund holders through familiar regulated structures. Custodial banks and institutional-grade service providers are exploring or entering the restaking market, signaling that the category has evolved from a crypto-native activity toward an institutional infrastructure consideration.
For institutions with existing ETH staking programs, the restaking evaluation question is whether the additional protocol-generated rewards from AVS participation justify the additional slashing exposure, operational complexity, and compliance requirements that restaking introduces. That is a risk management decision, not a yield optimization decision.
For institutions building new digital asset programs, the sequencing is clear: establish native staking infrastructure first, evaluate liquid staking as a capital efficiency layer second, and assess restaking as a third layer once the foundation is sound and the risk framework is explicitly designed for the additional exposure restaking creates.
Building an institutional restaking program? P2P.org provides non-custodial EigenLayer restaking infrastructure with validator-level reporting and operational safeguards designed for institutional requirements.
➡️ Explore P2P.org EigenLayer Restaking
For custodians, hedge funds, ETF issuers, exchanges, treasury teams, infrastructure engineers, staking product managers, and risk committees evaluating or initiating a restaking program, these are the foundational questions to answer before committing capital.
[ ] What is the audit history and code maturity of the restaking protocol?
[ ] Has each AVS in the approved list been independently assessed for slashing conditions, governance, and revenue model sustainability?
[ ] Does the restaking protocol use isolated stake allocation or per-vault slashing boundaries to limit correlated exposure?
[ ] What is the slashing history of the restaking protocol and each AVS in the approved list?
[ ] Does the operator run dedicated hardware with geographic redundancy and client diversity?
[ ] What is the operator's slashing history across all networks and AVSs they secure?
[ ] How does the operator manage signing keys for AVS participation alongside base layer validator operations?
[ ] Does the operator hold SOC 2 Type II or equivalent independent certification?
[ ] Are AVS rewards denominated in ETH, in the AVS's own token, or both?
[ ] Has your accounting team confirmed the tax treatment of AVS token rewards in your jurisdiction?
[ ] Does your compliance framework address the regulatory classification of AVS reward tokens applicable to your regulatory status?
[ ] Can the operator deliver validator-level reward attribution across all AVS reward streams for audit purposes?
[ ] Has your risk committee assessed stacked slashing exposure across your full AVS participation list?
[ ] Are concentration limits defined for exposure to any single AVS or operator?
[ ] Has your liquidity management framework been updated to reflect unbonding conditions at both the base layer and AVS level?
[ ] Has smart contract risk been assessed for both the restaking protocol and each AVS in your approved list?
[ ] Has the LRT protocol's audit history and code maturity been independently assessed?
[ ] Does your custody infrastructure support LRT holdings at the token level?
[ ] Has LRT depeg risk under stress conditions been modeled against your redemption obligations?
Restaking for institutions extends the utility of staked capital by allowing it to simultaneously secure additional services beyond the base proof-of-stake layer. For custodians, hedge funds, ETF issuers, exchanges, and treasury teams, that extension introduces stacked slashing exposure across multiple AVSs, operator concentration risk, AVS-level smart contract risk, and reward accounting complexity that is materially more demanding than native or liquid staking.
The infrastructure has matured, the regulatory environment has clarified, and institutional capital is moving into the category. The institutions that approach restaking as a risk management decision rather than a reward optimization exercise will be best positioned to build compliant, resilient programs as the category continues to develop.
Network conditions determine protocol-generated rewards and are variable. P2P.org does not control or set reward rates for base staking or AVS participation. Slashing risks are protocol-defined and client-borne at both the base layer and AVS level. Operational safeguards are implemented to reduce exposure, but do not eliminate protocol-level risk.
Restaking for institutions is the extension of staked capital beyond a single proof-of-stake network to simultaneously secure additional services called actively validated services. Institutions that restake allow their staked ETH or liquid staking tokens to secure multiple protocols at once, earning protocol-generated rewards from each AVS they opt into in addition to their base layer staking rewards. The extension introduces stacked slashing exposure, operator concentration risk, and AVS-level smart contract risk that must be explicitly assessed before any restaking program is designed.
Native staking locks capital to secure a single proof-of-stake network. Liquid staking issues a transferable receipt token at the point of staking, preserving capital flexibility while the underlying asset continues to participate in consensus. Restaking extends staked capital to secure additional services simultaneously, adding AVS-level slashing conditions and reward streams on top of the base layer staking program. Each layer introduces distinct risk categories that compound as the program extends across more AVSs.
An actively validated service is an external system that uses restaked capital as its economic security layer instead of bootstrapping its own validator set. AVSs include oracle networks, data availability layers, cross-chain bridges, decentralized sequencers, and verification services. Each AVS defines its own slashing conditions and reward structure. Institutions opting into an AVS accept those slashing conditions in exchange for the protocol-generated rewards the AVS distributes to operators and restakers.
Stacked slashing risk is the compounding slashing exposure that results from opting into multiple AVSs simultaneously. Native staking carries one set of slashing conditions at the base layer. Each AVS added to a restaking program adds an independent set of slashing conditions. A slashing event triggered by an AVS-level failure can result in permanent loss of a portion of the restaked capital, independent of the institution's base layer staking performance. Institutions must assess the slashing conditions of each AVS independently and model correlated slashing scenarios across their full restaking program.
A liquid restaking token is a receipt token issued by a liquid restaking protocol when an institution restakes ETH or an LST. It represents the restaked position, accrues the rewards of the restaking program, and remains transferable and composable. LRTs extend the capital efficiency logic of liquid staking tokens to the restaking layer, but compound the risk profile: smart contract risk at the LRT protocol layer and depeg risk in secondary markets stack on top of the AVS-level slashing, and smart contract risks that restaking itself introduces.
Operator selection determines uptime, AVS rule compliance, and slashing exposure across the restaking program. Institutions must evaluate operators across infrastructure architecture, client diversity, key management practices, AVS selection history, slashing record, governance participation policies, and independent certification such as SOC 2 Type II. The operator evaluation must be applied independently to each AVS the operator secures, not assessed once at the program level. Diversification across operators reduces concentration risk that would otherwise compound the existing AVS-level exposure.
The March 2026 SEC and CFTC joint interpretation explicitly excluded restaking from its covered protocol staking activities. Restaking remains legally uncertain at the federal level, and neither the SEC nor the CFTC has issued specific guidance on it to date. Institutions engaged in restaking should treat their programs as operating outside the scope of the March 2026 interpretation and consult counsel regarding both securities law and CEA implications before allocating capital.
About P2P.org
Founded in 2018, P2P.org helps institutional capital protect digital asset yield across non-custodial staking infrastructure and curated DeFi strategies. With over $10B in assets secured and operating on 40+ proof-of-stake networks, P2P.org maintains a zero-slashing-incident track record, is trusted by over 190 institutional clients and is SOC 2 Type II attested. To explore how P2P.org can support your institution's staking or DeFi infrastructure needs, get in touch with our team.
Disclaimer
This material is provided for informational purposes only and does not constitute investment, financial, legal, or tax advice. P2P.org accepts no liability for any actions taken based on it. Latency and performance figures referenced are estimates based on internal benchmarks and may vary depending on network conditions, geography, and client infrastructure. Past performance is not indicative of future results.
<h2 id="series-defi-infrastructure-for-institutions">Series: DeFi Infrastructure for Institutions</h2><p><a href="http://p2p.org/?ref=p2p.org">P2P.org</a>'s content series for regulated institutions evaluating onchain capital allocation. Each article addresses a specific infrastructure, governance, or compliance dimension that determines whether a DeFi allocation can clear institutional approval and operate within mandate.</p><p>This is the third and closing article of the third trilogy of the series, completing the institutional profile sequence. <a href="https://p2p.org/economy/defi-vault-allocation-for-custodians-infrastructure-requirements-and-risk-considerations/">The first article</a> examined the infrastructure requirements for custodians. <a href="https://p2p.org/economy/how-hedge-funds-are-approaching-on-chain-yield-strategies-in-2026/">The second article</a> examined how hedge funds are approaching onchain yield strategies. This article examines stablecoin onchain yield strategies for treasury functions at financial institutions and asset managers.</p><p>The previous trilogy examined how conflict-of-interest frameworks across MiFID II, AIFMD II, and IOSCO's DeFi recommendations are converging on the curator model: <a href="https://p2p.org/economy/conflict-of-interest-defi-vault-regulation-institutional/">How Conflict-of-Interest Regulatory Frameworks Are Catching Up to the Curator Model</a></p><p><em>Previously in this series: </em><a href="https://p2p.org/economy/how-hedge-funds-are-approaching-on-chain-yield-strategies-in-2026/"><em>How Hedge Funds Are Approaching Onchain Yield Strategies in 2026</em></a></p><hr><h2 id="learnings-for-busy-readers">Learnings for Busy Readers</h2><p>Short on time? Here are the key takeaways. For the full analysis and supporting data, continue reading below.</p><ul><li>The stablecoin market has crossed $315 billion in total supply as of mid-2026. Annual stablecoin transaction volumes exceed $45 trillion, surpassing traditional payment networks. Treasury functions at financial institutions and asset managers are holding material stablecoin balances that generate no return, while the onchain yield infrastructure to put those balances to work at 5 to 8% APY is available, auditable, and increasingly regulated.</li><li>The GENIUS Act prohibits payment stablecoin issuers from paying yield directly to holders, creating a structural separation that shapes how all stablecoin yield products work in 2026. Yield generation must happen at the asset deployment layer, not the stablecoin issuer layer. Treasury teams need to understand this distinction before evaluating any stablecoin yield product: the stablecoin is the vehicle, not the return.</li><li>Stablecoin yield in 2026 is a tiered stack, not a single rate. The four primary tiers for institutional treasury mandates are tokenized money market funds at the capital-preservation end, curated DeFi lending vaults in the middle, real-world asset vaults for lower crypto-correlated yield, and yield-bearing stablecoin wrappers for passive deployment. Each tier has a distinct risk profile and governance requirement.</li><li>The governance infrastructure requirement for treasury teams interacting with DeFi vault protocols is the same as for custodians and hedge funds: pre-execution mandate validation, exportable compliance logs, and contractual role separation between the curator and the infrastructure layer.</li><li>The regulatory environment is supportive but evolving. The GENIUS Act provides US regulatory clarity. MiCA governs EU stablecoin operations. Both frameworks create compliance obligations for treasury teams that go beyond simply choosing a yield-bearing product.</li></ul><h2 id="introduction">Introduction</h2><p>Treasury functions at financial institutions, exchanges, asset managers, and neobanks are holding stablecoin balances that have grown materially over the past two years. The stablecoin market has crossed $315 billion in total supply as of mid-2026, with annual transaction volumes exceeding $45 trillion, surpassing traditional payment networks. Public companies, DAOs, fintechs, and crypto-native operating businesses collectively hold over $35 billion in onchain stablecoin reserves as of Q1 2026. Source: <a href="https://www.sygnum.com/blog/2025/05/30/institutional-defi-in-2025-the-disconnect-between-infrastructure-and-allocation/?ref=p2p.org">Sygnum Bank</a></p><p>For most of these treasury teams, those balances are idle. Stablecoins held in custody generate no return. The operational rationale for holding stablecoin balances, settling transactions faster, moving capital across chains without correspondent banking friction, and managing operational floats across multiple jurisdictions is strong. But holding is not the same as deploying. And the gap between a stablecoin balance earning nothing and the same balance deployed into a curated DeFi lending vault earning 5 to 8% APY is now wide enough to attract treasury committee attention across the institutional spectrum.</p><p>According to a June 2025 EY-Parthenon survey, 13% of financial institutions and corporates globally are already using stablecoins, with 54% of non-users expecting to adopt them within 6 to 12 months. The regulatory environment has moved to support that transition. The GENIUS Act, signed into law on July 18, 2025, established the first comprehensive federal framework for payment stablecoins in the US. MiCA governs stablecoin operations across all 27 EU member states. The compliance environment is now defined enough to navigate. Source: <a href="https://www.sygnum.com/blog/2025/05/30/institutional-defi-in-2025-the-disconnect-between-infrastructure-and-allocation/?ref=p2p.org">Sygnum Bank</a></p><p>But regulatory clarity on stablecoins does not automatically produce operational clarity on stablecoin yield. The infrastructure requirements for holding stablecoins and deploying them into onchain yield strategies within a treasury mandate are related but not equivalent. This article examines what those requirements look like in practice, what the stablecoin yield stack looks like for institutional treasury mandates in 2026, and what the governance infrastructure requirement is for treasury teams interacting with DeFi vault protocols.</p><h2 id="the-genius-act-and-the-yield-separation-problem">The GENIUS Act and the Yield Separation Problem</h2><p>Before examining stablecoin yield strategies, treasury teams need to understand a structural feature of the regulatory environment that shapes how those strategies work.</p><p>The GENIUS Act, passed in July 2025, prohibits payment stablecoin issuers from paying interest or yield to stablecoin holders. This prohibition is significant. It means that USDC, USDT, and other payment stablecoins issued under the GENIUS Act framework cannot themselves generate yield for holders. The stablecoin is a transfer and settlement instrument. Yield generation must happen separately, at the asset deployment layer. Source: <a href="https://defiprime.com/defi-vaults-guide?ref=p2p.org">DeFi Prime</a></p><p>This creates a structural separation that treasury teams need to internalize before evaluating any stablecoin yield product. The stablecoin is the vehicle. The yield-generating instrument is a separate product that the treasury team deploys stablecoins into: a tokenized money market fund, a DeFi lending vault, a yield-bearing stablecoin wrapper issued by a separate entity, or a real-world asset vault. Each of these products has its own risk profile, its own regulatory classification, and its own governance requirement. The yield does not come from the stablecoin. It comes from what the stablecoin is deployed into.</p><p>Under the GENIUS Act and similar regulations, stablecoins must be backed one-to-one by high-quality reserves including US dollars, insured bank deposits, and short-term US Treasuries, with monthly public disclosures and management certifications. These reserve requirements apply to the issuer, not to the treasury team deploying the stablecoin. But they matter for treasury evaluation: the quality of the reserve backing determines the stability of the stablecoin itself, which is the entry point for any yield strategy built on top of it.</p><h2 id="the-stablecoin-yield-stack-for-institutional-treasury">The Stablecoin Yield Stack for Institutional Treasury</h2><p>Stablecoin yield in 2026 is no longer a single number. The onchain dollar market has stratified along the same yield curve treasurers already know offchain: cash management at the short end, savings rates in the middle, basis trades and structured strategies at the long end. For institutional treasury mandates, four tiers within that stack are relevant, each mapped to a specific mandate type and risk tolerance. Source: <a href="https://arxiv.org/html/2512.11976v1?ref=p2p.org">arXiv</a></p><figure class="kg-card kg-image-card kg-card-hascaption"><img src="https://p2p.org/economy/content/images/2026/07/stablecoin-yield-stack-institutional-treasury.jpg.png" class="kg-image" alt="A horizontal four-tier risk spectrum diagram showing the stablecoin yield stack for institutional treasury mandates. From left to right: tokenized money market funds at the capital preservation end with T-bill rate minus fee yield, curated DeFi lending vaults at 4 to 9% APY with smart contract and curator risk, real-world asset vaults with offchain-backed yield and lower crypto correlation, and yield-bearing stablecoin wrappers at the right with passive deployment and wrapper smart contract risk." loading="lazy" width="1600" height="849" srcset="https://p2p.org/economy/content/images/size/w600/2026/07/stablecoin-yield-stack-institutional-treasury.jpg.png 600w, https://p2p.org/economy/content/images/size/w1000/2026/07/stablecoin-yield-stack-institutional-treasury.jpg.png 1000w, https://p2p.org/economy/content/images/2026/07/stablecoin-yield-stack-institutional-treasury.jpg.png 1600w" sizes="(min-width: 720px) 720px"><figcaption><span style="white-space: pre-wrap;">The stablecoin yield stack for institutional treasury mandates, from lowest to highest risk across four strategy tiers.</span></figcaption></figure><p></p><h3 id="tier-1-tokenized-money-market-funds">Tier 1: Tokenized money market funds</h3><p>The lowest-risk entry point for institutional treasury stablecoin yield. Funds like BlackRock's BUIDL with $2.4 billion AUM as of March 2026, Ondo's USDY, Franklin Templeton's BENJI, and Superstate's USTB hold real US Treasury bills and pass the yield through onchain. The yield is the T-bill rate minus a 15 to 50 basis point management fee. These products are appropriate for treasury mandates with capital preservation as the primary objective, where the governance question is essentially the same as for a traditional money market fund: issuer quality, reserve transparency, and redemption mechanics. The onchain layer adds transparency, 24/7 accessibility, and composability. The risk profile is comparable to a regulated money market fund. Source: <a href="https://www.zircuit.com/en/blog/vault-infrastructure-the-institutional-upgrade-traditional-asset-management-has-been-waiting-for?ref=p2p.org">Zircuit</a></p><h3 id="tier-2-curated-defi-lending-vaults">Tier 2: Curated DeFi lending vaults</h3><p><strong>.</strong> The primary yield generation tier for institutional treasury teams willing to accept smart contract risk in exchange for materially higher returns. Deposits held in onchain lending markets have grown by over 60% year-on-year. Across leading collateralised lending platforms, 30-day lending yields on USDC ranged from 4% to 9% as of June 2025. Curated vaults on Morpho, Aave, and Euler allocate depositor stablecoins across lending markets according to the curator's strategy, generating yield from borrower interest. The governance requirement for this tier is material: pre-execution mandate validation, exportable compliance logs, and contractual role separation between the curator and the infrastructure layer. Without this governance infrastructure, the treasury team cannot demonstrate mandate alignment to its board, auditors, or regulators.</p><h3 id="tier-3-real-world-asset-vaults">Tier 3: Real-world asset vaults</h3><p>For treasury mandates requiring yield with lower correlation to crypto market conditions, RWA vaults offer returns derived from offchain economic activity, including government debt, private credit, and money market instruments. The value of tokenized real-world assets surpassed $7 billion, with tokenized T-bill products adopted and integrated into the DeFi ecosystem. These products sit between Tier 1 and Tier 2 in risk profile: they carry smart contract risk from the onchain layer and credit or duration risk from the underlying assets, but they are less exposed to crypto-native market volatility. The governance requirement includes verifying that the offchain asset backing is accurately and continuously represented onchain, which adds a due diligence dimension beyond standard vault evaluation.</p><h3 id="tier-4-yield-bearing-stablecoin-wrappers">Tier 4: Yield-bearing stablecoin wrappers</h3><p>The most passive deployment option for treasury teams that want yield without active position management. Yield-bearing wrappers like sUSDS, sDAI, and USDY are plain ERC-20 tokens that can be used as collateral elsewhere, allowing treasury teams to stack passive yield underneath whatever deployment they do next, instead of parking capital in an isolated account where the yield stops the moment capital needs to move. The risk profile is the underlying yield source plus wrapper smart contract risk. For treasury mandates with high liquidity requirements, the composability of yield-bearing wrappers makes them a useful base layer. Source: <a href="https://www.thetokendispatch.com/p/defis-risk-layer?ref=p2p.org">Thetokendispatch</a></p><h2 id="the-governance-infrastructure-requirement-for-treasury-teams">The Governance Infrastructure Requirement for Treasury Teams</h2><p>The governance infrastructure requirement for treasury functions interacting with DeFi vault protocols is structurally the same as for custodians and hedge funds, with one additional dimension specific to treasury operations: board and audit committee reporting.</p><h3 id="1-pre-execution-mandate-validation">1. Pre-execution mandate validation</h3><p>A treasury function operating under a documented investment policy statement needs to demonstrate at every execution point that its stablecoin deployments are within mandate parameters. Concentration limits across protocols, approved counterparty lists, maximum smart contract risk exposure, and liquidity requirements are all parameters that must be validated before any vault interaction executes. The curator managing the vault has no visibility into any individual treasury team's mandate. The validation layer is the treasury team's responsibility, not the vault's.</p><h3 id="2-exportable-compliance-logs">2. Exportable compliance logs</h3><p>Treasury functions at regulated financial institutions face audit requirements from internal audit, external auditors, and regulatory examiners. Each of these functions needs to be able to verify that stablecoin deployments were within mandate parameters at every historical point. A vault dashboard is not an audit trail. The compliance log must be sequential, timestamped, and exportable in a format that satisfies the institution's audit infrastructure.</p><h3 id="3-conflict-of-interest-documentation">3. Conflict of interest documentation</h3><p>As the second trilogy of this series established, the curator model creates a structural conflict of interest that MiFID II, AIFMD II, and MiCA all require to be identified, documented, and managed. Treasury functions at regulated institutions face the same requirement through their compliance frameworks. The independent validation layer is the primary control. Its existence and operation need to be documented in the institution's risk and governance framework.</p><h3 id="4-board-and-audit-committee-reporting">4. Board and audit committee reporting</h3><p>Beyond the regulatory compliance requirements that custodians and hedge funds share, treasury functions face specific governance obligations to their board and audit committees. Stablecoin yield positions need to be reported at fair value, with appropriate disclosure of the smart contract, curator concentration, and liquidity risks specific to each strategy tier. Board members and audit committee chairs evaluating stablecoin yield exposure for the first time will ask questions that require the same structural answers as LP due diligence: what is the mandate alignment mechanism, what does the audit trail look like, and what happens in a stress scenario?</p><hr><blockquote><strong>The institutional digital asset space moves fast.</strong><br><br>Our subscribers get structured analysis across staking, DeFi vaults, and regulation through <em>DeFi Dispatch</em>, <em>Institutional Lens</em>, <em>DeFi Infrastructure for Institutions</em>, and <em>Legal Layer</em>.<br><br>No noise. Just the signals that matter.<br><br><strong>Subscribe to the newsletter at the bottom of this page.</strong></blockquote><hr><h2 id="the-regulatory-environment-for-institutional-stablecoin-treasury">The Regulatory Environment for Institutional Stablecoin Treasury</h2><p>Treasury functions at financial institutions operating across multiple jurisdictions face a regulatory environment that has clarified materially in 2025 and 2026 but remains complex in its cross-border dimensions.</p><p>In the US, the GENIUS Act established the first comprehensive federal framework for payment stablecoins. On April 8, 2026, FinCEN and OFAC issued a joint Notice of Proposed Rulemaking to implement AML and sanctions compliance provisions of the GENIUS Act for permitted payment stablecoin issuers, treating them as financial institutions under the Bank Secrecy Act and requiring AML/CFT programs and sanctions compliance. For treasury teams at US financial institutions, this means their stablecoin operations are subject to the same BSA and OFAC compliance framework as their traditional financial activities. The compliance infrastructure for stablecoin treasury management is not separate from the institution's existing AML and sanctions framework. It is an extension of it. Source: <a href="https://www.rapidinnovation.io/post/top-defi-protocols-to-look-for-in-2024?ref=p2p.org">Rapid Innovation</a></p><p>In the EU, MiCA governs stablecoin operations through its e-money token and asset-referenced token frameworks, with full authorisation required for all issuers operating in the EU. The MiCA framework requires reserve backing, redemption at par, and compliance with the same conflict of interest, audit trail, and client asset safeguarding requirements that MiCA imposes on CASPs more broadly.</p><p>For multinational institutions, navigating this patchwork requires careful attention to jurisdictional requirements and the selection of stablecoin issuers with appropriate licences in target markets. The practical implication for treasury teams is that stablecoin selection is not just a yield and risk question. It is a regulatory compliance question that needs to be evaluated on a jurisdiction-by-jurisdiction basis before any deployment. Source: <a href="https://www.calibraint.com/blog/defi-regulatory-compliance-sec-cftc-2025?ref=p2p.org">Calibraint</a></p><h2 id="what-this-means-for-treasury-functions-evaluating-onchain-yield">What This Means for Treasury Functions Evaluating Onchain Yield</h2><p>The treasury functions at financial institutions that are building durable stablecoin yield programs in 2026 are not the ones evaluating headline APY rates across DeFi protocols. They are the ones that have mapped the yield stack against their mandate parameters, built or sourced the governance infrastructure to validate every deployment, and structured their onchain positions within a framework that their boards, auditors, and regulators can examine.</p><p>Yield-bearing stablecoins have grown from $9.5 billion at the start of 2025 to more than $20 billion, with average yields around 5%, slightly above traditional money market rates. The yield opportunity is documented, growing, and in many cases accessible within conservative treasury mandates through Tier 1 and Tier 2 strategies. The question for treasury teams is not whether stablecoin yield is available. The question is whether the governance infrastructure governing the deployment can demonstrate mandate alignment at every execution point to every stakeholder that needs to see it. Source: <a href="https://www.sygnum.com/blog/2025/05/30/institutional-defi-in-2025-the-disconnect-between-infrastructure-and-allocation/?ref=p2p.org">Sygnum Bank</a></p><p><a href="https://p2p.org/?ref=p2p.org#form">Talk to our team</a> if you are evaluating how <a href="http://p2p.org/?ref=p2p.org">P2P.org</a>'s protection layer integrates with treasury infrastructure for institutional stablecoin yield strategies.</p><h2 id="key-takeaway">Key Takeaway</h2><p>Stablecoin yield for institutional treasury mandates is no longer a frontier question. The protocols exist, the regulatory frameworks are defined, and the yield spreads over traditional money market rates are wide enough to attract treasury committee attention across the institutional spectrum. What remains is the governance question.</p><p>The GENIUS Act's yield separation structure means treasury teams must evaluate stablecoin yield at the asset deployment layer, not the issuer layer. The stablecoin yield stack in 2026 spans four tiers from tokenized money market funds to yield-bearing wrappers, each with a distinct risk profile and mandate fit. And the governance infrastructure that makes deployment within mandate demonstrable, pre-execution validation, exportable compliance logs, and board-level reporting, is the same infrastructure that the first trilogy of this series identified as the missing layer in DeFi vault architecture.</p><p>The treasury functions that build or source that governance infrastructure now will capture the yield spread that idle stablecoin balances are currently leaving on the table. The ones who defer it will find the question increasingly difficult to answer when their boards ask why their stablecoin balances are generating nothing.</p><p><em>The DeFi Infrastructure for Institutions series continues. The next sequence examines how the protection layer operates in practice for specific products and integration use cases.</em></p><h2 id="frequently-asked-questions-faq">Frequently Asked Questions (FAQ)</h2><h3 id="why-cant-payment-stablecoins-like-usdc-pay-yield-directly-to-holders">Why can't payment stablecoins like USDC pay yield directly to holders?</h3><p>The GENIUS Act, signed into law on July 18, 2025, explicitly prohibits permitted payment stablecoin issuers from paying interest or yield to stablecoin holders. This prohibition reflects a policy decision to treat payment stablecoins as settlement instruments rather than investment products, avoiding the regulatory classification questions that yield-paying tokens would raise under securities and banking law. Yield generation must therefore happen at the asset deployment layer: treasury teams deploy stablecoins into yield-generating instruments such as tokenized money market funds, DeFi lending vaults, or RWA vaults, and earn yield from those instruments rather than from the stablecoin itself.</p><h3 id="what-is-the-difference-between-a-tokenized-money-market-fund-and-a-curated-defi-lending-vault-for-treasury-purposes">What is the difference between a tokenized money market fund and a curated DeFi lending vault for treasury purposes?</h3><p>A tokenized money market fund wraps short-duration government debt into an onchain token and passes the yield through to holders. The yield source is sovereign debt or government money market instruments, and the risk profile is comparable to a traditional money market fund with the addition of smart contract risk from the token wrapper. A curated DeFi lending vault deploys depositor stablecoins into DeFi lending markets and generates yield from borrower interest. The yield is higher, but the risk profile is materially different: smart contract risk from the vault and the underlying protocols, curator incentive misalignment, and liquidity risk from the underlying lending markets. For treasury mandates with capital preservation as the primary objective, Tier 1 is the appropriate starting point. For mandates with room for managed risk in exchange for yield above money market rates, Tier 2 becomes relevant.</p><h3 id="what-reserve-requirements-apply-to-stablecoins-under-the-genius-act">What reserve requirements apply to stablecoins under the GENIUS Act?</h3><p>The GENIUS Act requires permitted payment stablecoin issuers to maintain one-to-one backing with high-quality liquid assets, including US dollars, insured bank deposits, and short-term US Treasuries with a maximum 93-day maturity. Reserves cannot be rehypothecated or commingled with the issuer's own funds. Monthly public disclosures of reserve composition and outstanding stablecoins are required, along with monthly management certifications and annual audited financial statements for large issuers. These requirements apply to the issuer, not to the treasury team deploying the stablecoin, but they are material to stablecoin selection for treasury operations because reserve quality determines the stability of the instrument at the base of any yield strategy.</p><h3 id="how-does-the-governance-infrastructure-requirement-for-treasury-differ-from-that-for-hedge-funds">How does the governance infrastructure requirement for treasury differ from that for hedge funds?</h3><p>The core infrastructure requirements are similar: pre-execution mandate validation, exportable compliance logs, and contractual role separation between the curator and the infrastructure layer. The primary additional requirement for treasury functions at regulated financial institutions is board and audit committee reporting: stablecoin yield positions need to be reported at fair value, with appropriate disclosure of smart contract, curator concentration, and liquidity risks specific to each strategy tier. Board members and audit committee chairs evaluating stablecoin yield exposure for the first time will ask the same structural questions as regulatory examiners. The governance infrastructure needs to produce answers that satisfy both audiences.</p><h3 id="what-does-multi-jurisdictional-regulatory-compliance-mean-for-treasury-teams-deploying-stablecoins-across-borders">What does multi-jurisdictional regulatory compliance mean for treasury teams deploying stablecoins across borders?</h3><p>Treasury functions at financial institutions operating across multiple jurisdictions face different regulatory requirements for stablecoin operations in each market. In the US, stablecoin operations are subject to the GENIUS Act framework and BSA/OFAC compliance obligations through FinCEN and OFAC's April 2026 joint Notice of Proposed Rulemaking. In the EU, MiCA governs stablecoin operations through its e-money token framework, requiring issuer authorisation, reserve backing, and compliance with MiCA's conflict of interest and client asset safeguarding requirements. Other jurisdictions, including Hong Kong, Singapore, and the UAE have their own frameworks. The practical implication is that stablecoin selection needs to account for the regulatory status of the issuer in each jurisdiction where the treasury operates, not just in the home jurisdiction.</p><hr><p><strong>About </strong><a href="http://p2p.org/?ref=p2p.org"><strong>P2P.org</strong></a></p><p><a href="http://p2p.org/?ref=p2p.org">P2P.org</a> builds the protection layer that sits between regulated institutions and DeFi execution environments, independently of the curators who manage allocation strategies. If you are evaluating the infrastructure requirements for a DeFi allocation program, <a href="https://p2p.org/?ref=p2p.org#form">reach out to our team of experts</a>.</p><hr><p><strong>Disclaimer</strong></p><p>This article is provided for informational purposes only and does not constitute legal, regulatory, compliance, or investment advice. Regulatory obligations may vary depending on jurisdiction and specific business activities. Readers should consult their own legal and compliance advisors regarding applicable requirements.</p>
from p2p validator