Blog

<hr><h2 id="series-hub-institutional-staking">Series: Hub | Institutional Staking</h2><p>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.</p><p>Previously in the series: <a href="https://p2p.org/economy/institutional-defi-infrastructure/">Institutional DeFi Infrastructure: A Complete Guide for Funds, Custodians, and Treasury Teams</a></p><hr><h2 id="learnings-for-busy-readers">Learnings for Busy Readers</h2><p>What this article covers:</p><ul><li>What liquid staking for institutions is and how it differs from native staking.</li><li>How liquid staking tokens work and what they represent.</li><li>The capital efficiency case for institutional liquid staking programs.</li><li>The risk categories specific to liquid staking.</li><li>How LST custody and accounting differ from native staked assets.</li><li>What the regulatory treatment of liquid staking looks like in 2026.</li><li>How liquid staking integrates with ETF and ETP product structures.</li><li>A due diligence checklist for evaluating liquid staking programs.</li></ul><p><strong>The core argument</strong>: Liquid staking solves the liquidity problem of native staking by issuing a transferable token that represents a staked position. For institutions, that solution introduces a distinct risk profile, including smart contract exposure, LST depeg risk, and accounting classification complexity that requires explicit assessment before any program is designed.</p><h2 id="introduction">Introduction</h2><p>Liquid staking for institutions has moved from a capital efficiency experiment to a core operational consideration. In Q2 2025, liquid staking accounted for approximately 27% of total DeFi TVL. By August 2025, liquid staking TVL hit a record of over $86 billion, representing more than 50% of total DeFi TVL at that point. In Q3 2025, liquid staking and restaking combined represented over 45% of TVL across Ethereum equivalents. Source: <a href="https://thedefiant.io/news/defi/liquid-staking-tvl-hits-record-usd86b-amid-eth-rally-and-growing-institutional-adoption?ref=p2p.org">The Defiant</a></p><p>The regulatory environment has clarified materially. The March 2026 SEC and CFTC joint interpretation confirmed that liquid staking does not constitute a securities transaction. For compliance teams that had blocked LST exposure pending regulatory clarity, that barrier is now removed. The question shifts from whether an institution can participate to whether it should, and under what framework. Source: <a href="https://www.ropesgray.com/en/insights/alerts/2026/03/sec-and-cftc-issue-landmark-joint-guidance-on-classification-of-crypto-assets?ref=p2p.org">RopesGray</a></p><p>For custodians, funds, ETF issuers, and treasury teams, the question is now operational: what is liquid staking exactly, how do liquid staking tokens work, what are the risk categories that differ from native staking, and what does an institutional-grade liquid staking program actually require?</p><p>This article answers those questions from the ground up.</p><h2 id="what-liquid-staking-for-institutions-is">What Liquid Staking for Institutions Is</h2><p>Native staking locks capital in a proof-of-stake protocol for a defined unbonding period. On Ethereum, that period is variable but typically several days. On Solana, it is approximately four to five days. During that period, the staked capital is not accessible. It cannot be deployed elsewhere, used as collateral, or redeemed on demand.</p><p>Liquid staking solves this constraint by issuing a receipt token at the point of staking. When an institution stakes ETH through a liquid staking protocol, it receives a liquid staking token, commonly known as an LST, in return. The LST represents the staked position and accrues the protocol rewards associated with it. The LST is transferable and composable. It can be traded, used as collateral in lending protocols, deployed in DeFi allocation programs, or held as a productive asset while the underlying ETH continues to participate in consensus and accrue protocol-generated rewards.</p><p>The staked ETH remains locked in the protocol. The LST circulates freely. The institution holds capital flexibility without exiting its staking position.</p><figure class="kg-card kg-image-card kg-card-hascaption"><img src="https://p2p.org/economy/content/images/2026/06/p2p-liquid-vs-native-staking-comparison.jpeg" class="kg-image" alt="A two-panel comparison diagram. The left panel shows native staking: institution deposits ETH, ETH locks in the protocol, rewards accrue, and capital remains inaccessible until unbonding completes. The right panel shows liquid staking: institution deposits ETH, the protocol locks ETH while simultaneously issuing an LST to the institution, rewards accrue into the LST value, and capital remains transferable and deployable throughout." loading="lazy" width="1600" height="900" srcset="https://p2p.org/economy/content/images/size/w600/2026/06/p2p-liquid-vs-native-staking-comparison.jpeg 600w, https://p2p.org/economy/content/images/size/w1000/2026/06/p2p-liquid-vs-native-staking-comparison.jpeg 1000w, https://p2p.org/economy/content/images/2026/06/p2p-liquid-vs-native-staking-comparison.jpeg 1600w" sizes="(min-width: 720px) 720px"><figcaption><i><em class="italic" style="white-space: pre-wrap;">Native staking locks capital until unbonding completes. Liquid staking issues an LST at the point of deposit, keeping the institution liquid while the underlying asset continues participating in consensus.</em></i></figcaption></figure><p>By early 2026, major asset managers were no longer satisfied with keeping digital assets in passive cold storage, where holdings lose value against inflationary issuance. Instead, they are demanding that staking be embedded directly into their custody workflows with clear segregation of duties, auditable reporting, and strict compliance controls. Source: <a href="https://p2p.org/economy/validator-due-diligence-framework-what-institutions-really-need-to-evaluate/">P2P.org</a></p><h2 id="how-liquid-staking-tokens-work">How Liquid Staking Tokens Work</h2><p>When an institution deposits ETH into a liquid staking protocol, the protocol stakes that ETH through its validator network and issues an LST representing the deposited position. Different protocols use different LST designs.</p><h3 id="rebasing-tokens">Rebasing tokens</h3><p>These automatically adjust the holder's token balance to reflect accrued protocol rewards. If an institution holds 100 stETH and the protocol accrues rewards, the balance increases to reflect those rewards. The token price stays pegged to the underlying asset.</p><h3 id="reward-bearing-tokens">Reward-bearing tokens</h3><p>These maintain a fixed balance but appreciate in value relative to the underlying asset as protocol rewards accrue. An institution holding rETH holds a fixed number of tokens, but each token becomes redeemable for a growing quantity of ETH over time.</p><p>Both designs achieve the same economic outcome: the institution captures protocol-generated rewards while holding a liquid, transferable asset. The difference is in accounting treatment, which matters significantly for institutional reporting and tax purposes.</p><p>With 78% of institutional investors indicating interest in regulated staking derivatives, compliant liquid staking services represent a $15 billion addressable market currently underserved by existing providers. Source: <a href="https://coinshares.com/us/insights/knowledge/institutional-staking-on-the-rise/?ref=p2p.org">CoinShares</a></p><h2 id="the-capital-efficiency-case-for-institutional-liquid-staking">The Capital Efficiency Case for Institutional Liquid Staking</h2><p>The primary institutional argument for liquid staking over native staking is capital efficiency. Native staking immobilizes capital for the duration of the unbonding period. Liquid staking returns a productive, transferable asset that can be deployed further while the underlying position continues generating protocol-defined rewards.</p><p>For institutions with active treasury management programs, this changes the participation calculus. Rather than choosing between staking participation and capital availability, an institution holding LSTs captures both. The LST can serve as collateral in an approved lending protocol. It can be included in a DeFi allocation program through P2P.org's vault infrastructure, where mandate validation at the transaction level ensures every deployment remains within the institution's approved parameters. It can be held as productive collateral in structured products.</p><p>On Solana, the liquid staking ratio rose from 11.6% to 17.6% quarter-on-quarter in Q4 2025, the largest single-quarter jump on record, with ETF issuers routing assets through liquid staking protocols as a mechanism to bring protocol-generated staking rewards to investors through regulated products. Source: <a href="https://coinlaw.io/bitcoin-staking-statistics/?ref=p2p.org">CoinLaw</a></p><p>For treasury teams managing long-duration digital asset holdings, liquid staking also addresses the dilution mechanics of holding unstaked assets on networks where new tokens are continuously issued to validators and delegators. Participation offsets that dilution while preserving capital flexibility that native staking does not.</p><h2 id="the-risk-categories-specific-to-liquid-staking">The Risk Categories Specific to Liquid Staking</h2><p>Liquid staking introduces a risk profile that differs from native staking in several material ways. Each category requires explicit assessment before any institutional program is designed.</p><h3 id="smart-contract-risk">Smart contract risk</h3><p>Liquid staking protocols operate on smart contracts. The LST is issued, managed, and redeemed through protocol code. A vulnerability in that code can result in loss of capital or failure to redeem the LST for the underlying asset. This risk does not exist in native staking at the protocol layer. Institutions evaluating liquid staking must assess the audit history, code maturity, and upgrade governance of any protocol they consider.</p><h3 id="lst-depeg-risk">LST depeg risk</h3><p>An LST is only as liquid as the secondary market that trades it. Under normal conditions, LSTs trade close to the value of their underlying staked assets. Under stress conditions, that relationship can break. During the June 2022 liquidity crisis, stETH traded at approximately a 5% discount to ETH on secondary markets as withdrawal demand exceeded available liquidity, demonstrating that LSTs can decouple from their peg under stress conditions even when the underlying staking protocol remains technically solvent. This risk is structural, not idiosyncratic: any LST is subject to depeg if secondary market liquidity is insufficient to absorb redemption volume during a broad market drawdown. For custodians and funds managing redemption obligations, this is a material balance sheet consideration.</p><h3 id="custody-and-accounting-complexity">Custody and accounting complexity</h3><p>LSTs are tokens, not native staking positions. Their custody, accounting, and tax treatment differ from native staked assets and vary by jurisdiction. The treatment of LSTs for accounting, tax reporting, and regulatory classification may differ from native staked positions depending on jurisdiction. This is an active area of legal development and warrants specific advice for each institution. Institutions must confirm that their custody infrastructure supports LST holdings and that their accounting framework handles rebasing token balance adjustments and reward-bearing token appreciation correctly.</p><h3 id="protocol-concentration-risk">Protocol concentration risk</h3><p>The liquid staking market is structurally concentrated. Lido's TVL reached approximately $41 billion in August 2025, making it the leading liquid staking platform by market share. Institutions allocating through a single protocol carry significant counterparty concentration to that protocol's governance, upgrade decisions, and smart contract risk profile. Diversification across protocols is an institutional risk management consideration that does not arise in native staking.</p><h3 id="regulatory-classification-risk">Regulatory classification risk</h3><p>While the March 2026 SEC and CFTC ruling removed the primary US securities law uncertainty, the regulatory treatment of LSTs for custody obligations, capital treatment, and reporting requirements continues to evolve. In EU-regulated markets, MiCA requires licensed custodial platforms to segregate client assets from firm capital and maintain mandatory capital buffers. Institutions operating across multiple jurisdictions must assess the classification and compliance requirements for LST holdings in each operating market.</p><h2 id="lst-custody-and-accounting-in-practice">LST Custody and Accounting in Practice</h2><p>Holding an LST in an institutional context is not operationally equivalent to holding the underlying staked asset. Several dimensions require explicit design.</p><h3 id="custody-infrastructure">Custody infrastructure</h3><p>The institution's custody provider must support LST holdings at the token level. This means wallet infrastructure capable of receiving, holding, and transferring the specific token standard of each LST. Custody providers that support ETH staking natively may not automatically support LST custody at the institutional level without additional configuration.</p><h3 id="rebasing-token-accounting">Rebasing token accounting</h3><p>For institutions holding rebasing LSTs, the automatic balance adjustment that reflects accrued protocol rewards creates accounting entries that must be captured correctly. Each rebase event represents a protocol reward distribution that requires recognition for tax and reporting purposes. This differs structurally from reward-bearing tokens, which appreciate in price rather than adjusting balance.</p><h3 id="nav-calculation">NAV calculation</h3><p>For funds and ETF issuers incorporating LSTs into regulated products, net asset value calculation requires a reliable, auditable price feed for each LST held. The price relationship between an LST and its underlying asset is not always a simple 1:1 peg. Funds must have a documented methodology for LST valuation that satisfies their auditors and regulators.</p><h3 id="segregation-of-duties">Segregation of duties</h3><p>Institutions are demanding that staking be embedded directly into their custody workflows with clear segregation of duties, auditable reporting, and strict compliance controls. For liquid staking specifically, this means documented processes for LST issuance, transfer, redemption, and protocol reward recognition that satisfy both internal audit and external regulatory requirements. Source: <a href="https://p2p.org/economy/validator-due-diligence-framework-what-institutions-really-need-to-evaluate/">P2P.org</a></p><h2 id="liquid-staking-in-etf-and-etp-product-structures">Liquid Staking in ETF and ETP Product Structures</h2><p>The integration of liquid staking into regulated investment products is one of the most significant institutional developments of 2025 and 2026. ETF issuers routed assets through liquid staking protocols as a mechanism to bring protocol-generated staking rewards to investors through regulated products, with Bloomberg Intelligence ETF analyst Eric Balchunas calling Bitwise's BSOL the best ETF debut of 2025 across any asset class. Source: <a href="https://coinlaw.io/bitcoin-staking-statistics/?ref=p2p.org">CoinLaw</a></p><p>For ETF and ETP issuers, liquid staking offers a mechanism to participate in protocol reward accrual on digital asset holdings within a regulated product structure, without requiring the product to hold illiquid native staked positions. The LST is a liquid, transferable asset that can be held, valued, and redeemed within the operational constraints of a regulated fund vehicle.</p><p>Nasdaq filed a proposal in February 2026 to list the VanEck JitoSOL Solana Liquid Staking ETF, the first attempt to offer a regulated product tied directly to an LST. The product design question for ETF issuers is no longer whether to incorporate liquid staking but how to do so in a way that satisfies custody, valuation, and compliance requirements at the fund level.</p><p>For custodians supporting ETF issuers, the implication is that LST custody capability is becoming a prerequisite for institutional client retention in staking-integrated product structures.</p><h2 id="the-regulatory-treatment-of-liquid-staking-for-institutions-in-2026">The Regulatory Treatment of Liquid Staking for Institutions in 2026</h2><p>The regulatory environment for liquid staking has clarified substantially since 2025. The March 2026 SEC and CFTC joint interpretation confirmed that liquid staking does not constitute a securities transaction in the United States across all four staking models: solo, self-custodial, custodial, and liquid. The SEC's August 2025 policy statement clarified that non-managerial staking functions by providers may avoid securities classification, a position that removed a significant overhang for institutions evaluating LST exposure across proof-of-stake networks.</p><p>In Europe, MiCA provides a framework for staking within licensed digital asset service providers, with requirements for asset segregation and capital adequacy that apply to custodial platforms holding LSTs on behalf of clients. The decentralization threshold test in the CLARITY Act is the operative mechanism that institutional compliance departments will use to classify multi-chain staking programs, DeFi vault deployments, and liquid staking token arrangements going forward.</p><p>Institutions should treat the current regulatory clarity as a floor, not a ceiling. The classification of LSTs for capital treatment, tax reporting, and cross-border holding requirements continues to develop. Each institution's legal and compliance advisors must assess the applicable requirements for their specific operating markets.</p><p>Network conditions determine protocol-generated rewards and are variable. P2P.org does not control or set reward rates.</p><h2 id="where-p2porg-supports-liquid-staking-for-institutions">Where P2P.org Supports Liquid Staking for Institutions</h2><p>P2P.org operates non-custodial ETH staking infrastructure for custodians, funds, ETF issuers, and treasury teams building both native and liquid staking programs. Validator-level reward reporting and operational safeguards are available for institutional requirements. Client assets remain under the institution's control throughout.</p><p>For institutions looking to combine liquid staking positions with DeFi allocation programs, P2P.org's vault infrastructure supports LST deployment into approved protocols with mandate validation at the transaction level. Every deployment is checked against the institution's parameters before execution.</p><p>Explore P2P.org's ETH staking infrastructure at <a href="https://eth.p2p.org/staking?ref=p2p.org">eth.p2p.org/staking</a>.</p><p>Building an institutional liquid staking program? P2P.org provides non-custodial ETH staking infrastructure with validator-level reporting and operational safeguards designed for institutional requirements. <a href="https://eth.p2p.org/staking?ref=p2p.org">Explore P2P.org ETH Staking</a></p><h2 id="due-diligence-checklist-evaluating-a-liquid-staking-for-institutions-program">Due Diligence Checklist: Evaluating a Liquid Staking for Institutions Program</h2><p>For custodians, hedge funds, ETF issuers, exchanges, treasury teams, infrastructure engineers, staking product managers, and risk committees evaluating or initiating a liquid staking program, these are the foundational questions to answer before committing capital.</p><h3 id="protocol-selection">Protocol selection</h3><p>[ ] What is the audit history and code maturity of the liquid staking protocol? <br>[ ] Who governs protocol upgrades, and how are governance decisions made? <br>[ ] What is the protocol's slashing history and mechanism for covering slashing losses? <br>[ ] Is the protocol's TVL and secondary market liquidity sufficient to support institutional redemption volumes?</p><h3 id="lst-type-and-accounting">LST type and accounting</h3><p>[ ] Is the LST a rebasing token or a reward-bearing token, and does your accounting framework handle both correctly? <br>[ ] Has your accounting team confirmed the tax treatment of LST protocol reward recognition in your jurisdiction? <br>[ ] Does your NAV calculation methodology support LST valuation for fund or ETP reporting purposes?</p><h3 id="custody-infrastructure-1">Custody infrastructure</h3><p>[ ] Does your custody provider support LST holdings at the token level for the specific protocols you intend to use? <br>[ ] Is there a documented process for LST issuance, transfer, redemption, and protocol reward recognition that satisfies audit requirements? <br>[ ] Does your custody arrangement maintain asset segregation as required under MiCA or applicable regulations?</p><h3 id="risk-management">Risk management</h3><p>[ ] Has your risk committee assessed LST depeg risk and its implications for your liquidity management framework? <br>[ ] Are concentration limits defined for exposure to any single liquid staking protocol? <br>[ ] Has smart contract risk been assessed for each protocol in your approved list?</p><h3 id="regulatory-compliance">Regulatory compliance</h3><p>[ ] Has legal confirmed the regulatory treatment of LST holdings in each jurisdiction where your institution operates? <br>[ ] Does your compliance framework address the LST custody obligations applicable to your regulatory status? <br>[ ] Is there a documented policy for how LST holdings are classified and reported under your applicable accounting standards?</p><h2 id="key-takeaway">Key Takeaway</h2><p>Liquid staking for institutions solves the capital immobilization problem of native staking by issuing a transferable token that represents a staked position and continues accruing protocol-generated rewards. For custodians, hedge funds, ETF issuers, exchanges, and treasury teams, that solution introduces a distinct risk profile: smart contract exposure, LST depeg risk under market stress, custody and accounting complexity, and protocol concentration. Each of these categories requires explicit assessment and mitigation as part of any institutional liquid staking program design.</p><p>The regulatory environment in 2026 has removed the primary legal barriers to institutional participation. The infrastructure has matured to support institutional-grade programs at scale. The institutions that build a rigorous foundation across protocol selection, custody architecture, and accounting framework now will be best positioned as liquid staking becomes a standard component of digital asset strategy across every institutional segment.</p><p>Network conditions determine protocol-generated rewards and are variable. P2P.org does not control or set reward rates. Smart contract risks are protocol-defined and client-borne. Operational safeguards are implemented to reduce exposure, but do not eliminate protocol-level risk.</p><h2 id="frequently-asked-questions-faq">Frequently Asked Questions (FAQ)<br></h2><h3 id="what-is-liquid-staking-for-institutions">What is liquid staking for institutions?</h3><p>Liquid staking for institutions is a staking participation model in which an institution deposits digital assets into a proof-of-stake protocol and receives a liquid staking token in return. The LST represents the staked position, accrues protocol-generated rewards, and remains transferable and composable throughout. Unlike native staking, which locks capital for the duration of the unbonding period, liquid staking allows institutions to maintain staking participation while retaining a liquid, deployable asset. It is used by custodians, funds, ETF issuers, exchanges, and treasury teams as a capital efficiency mechanism within broader digital asset programs.</p><h3 id="what-is-a-liquid-staking-token">What is a liquid staking token?</h3><p>A liquid staking token is a receipt token issued by a liquid staking protocol when an institution deposits assets for staking. It represents the deposited position and accrues the protocol rewards associated with it. LSTs come in two primary designs: rebasing tokens, which automatically adjust the holder's balance to reflect accrued protocol rewards, and reward-bearing tokens, which maintain a fixed balance but appreciate in value relative to the underlying asset as rewards accrue. The accounting treatment of each design differs and requires explicit assessment for institutional reporting and tax purposes.</p><h3 id="how-does-liquid-staking-differ-from-native-staking-for-institutions">How does liquid staking differ from native staking for institutions?</h3><p>In native staking, capital is locked in the protocol for an unbonding period and cannot be accessed or deployed until withdrawal is complete. In liquid staking, the protocol issues an LST at the point of staking that the institution can hold, transfer, or deploy while the underlying capital remains staked and accruing protocol-generated rewards. The capital efficiency advantage of liquid staking comes with additional risk layers: smart contract exposure, LST depeg risk, and custody and accounting complexity that do not exist in native staking.</p><h3 id="what-is-lst-depeg-risk">What is LST depeg risk?</h3><p>LST depeg risk is the possibility that an LST trades at a discount to its underlying staked asset on secondary markets. Under normal conditions, LSTs trade close to parity with the underlying asset. Under stress conditions, if redemption demand exceeds available secondary market liquidity, the LST can decouple from its peg even when the underlying staking protocol remains technically solvent. This risk is structural rather than idiosyncratic and affects any LST under sufficient market stress. Custodians and funds managing redemption obligations must assess LST depeg risk as part of their liquidity management framework.</p><h3 id="what-are-the-regulatory-requirements-for-holding-lsts-institutionally-in-2026">What are the regulatory requirements for holding LSTs institutionally in 2026?</h3><p>In the United States, the March 2026 SEC and CFTC joint interpretation confirmed that liquid staking does not constitute a securities transaction. In Europe, MiCA imposes asset segregation and capital adequacy requirements on licensed custodial platforms holding LSTs on behalf of clients. The tax treatment, capital classification, and cross-border holding requirements for LSTs continue to develop across jurisdictions. Each institution's legal and compliance advisors must assess the applicable requirements for their specific operating markets before allocating.</p><h3 id="how-does-liquid-staking-fit-into-etf-and-etp-product-structures">How does liquid staking fit into ETF and ETP product structures?</h3><p>Liquid staking tokens are liquid, transferable assets that can be held, valued, and redeemed within the operational constraints of regulated fund vehicles. ETF and ETP issuers have incorporated LSTs into product structures to participate in protocol reward accrual on digital asset holdings without requiring illiquid native staked positions. The primary design considerations for ETF issuers are LST valuation methodology for NAV calculation, custody infrastructure capable of supporting LST holdings at the token level, and compliance documentation for LST classification under applicable fund regulations.</p><h3 id="what-custody-infrastructure-is-required-for-institutional-liquid-staking">What custody infrastructure is required for institutional liquid staking?</h3><p>Institutional liquid staking requires custody infrastructure capable of holding, transferring, and redeeming the specific LST token standards of each protocol used. Custody providers must support rebasing token accounting if the institution holds rebasing LSTs, with correct recognition of automatic balance adjustments as protocol reward distributions. Asset segregation as required under MiCA or applicable regulations must be maintained throughout. Institutions should confirm that their custody provider's LST support has been validated for each protocol in their approved list before committing capital.</p><hr><h3 id="about-p2porg">About P2P.org</h3><p>P2P.org 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" rel="noreferrer">talk to our team</a>.</p><hr><h3 id="disclaimer">Disclaimer</h3><p>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.</p>

<h2 id="series-hub-institutional-defi-infrastructure">Series: Hub | Institutional DeFi Infrastructure</h2><p>The Institutional DeFi Infrastructure Hub is <a href="http://p2p.org/?ref=p2p.org">P2P.org</a>'s definitive reference for regulated institutions evaluating on-chain capital allocation. From vault architecture and mandate validation to the protection layer and compliance infrastructure, each article builds on the last to give funds, custodians, exchanges, and treasury teams a complete operational picture of what institutional DeFi participation actually requires.</p><p>New to institutional staking? Start with our foundation: <a href="https://p2p.org/economy/what-is-institutional-staking/">What Is Institutional Staking? A Complete Guide for Funds, Custodians, and Treasury Teams</a></p><hr><h2 id="introduction">Introduction</h2><p>DeFi has crossed a threshold. Total DeFi TVL across all chains sits at around $130 to $140 billion in early 2026, and on-chain DeFi lending captured roughly two-thirds of the record $73.6 billion crypto-collateralised lending market by late 2025. The protocols are mature, audited, and increasingly well understood. The regulatory environment is beginning to clarify. Institutional investors and asset managers are expected to expand their DeFi participation at a 32.55% CAGR through 2031, driven by regulated access, tokenisation, and payment-grade settlement.</p><p>Yet institutional allocation into DeFi remains structurally constrained. The gap is not protocol-level. The protocols work. The gap is infrastructure-level. Most DeFi vaults and yield products were designed for retail capital, and the assumptions built into that design create problems that regulated institutions cannot work around: no mandate validation before execution, no separation between the infrastructure layer and the strategy layer, and no audit trail compatible with institutional reporting requirements.</p><p>Institutional DeFi infrastructure is the layer that sits between regulated capital and DeFi execution environments. It is what makes on-chain allocation operationally viable for entities that operate under custody obligations, mandate constraints, risk committee governance, and regulatory reporting requirements.</p><p>This article explains what that infrastructure is, how it works, and what institutions evaluating DeFi participation need to understand before committing capital.</p><h2 id="learnings-for-busy-readers">Learnings for Busy Readers</h2><p>What this article covers:</p><ul><li>What institutional DeFi infrastructure is and what problem it solves</li><li>Why standard DeFi vault architecture falls short for regulated allocators</li><li>What the protection layer is and where it sits in the execution stack</li><li>The risk categories specific to institutional DeFi participation</li><li>How mandate validation works at the transaction level</li><li>What compliance infrastructure DeFi allocations require</li><li>Where P2P.org sits in this architecture</li><li>A due diligence checklist for evaluating institutional DeFi infrastructure</li></ul><p>The core argument: Institutional DeFi infrastructure is not a wrapper around DeFi. It is an independent execution layer that validates every transaction against mandate parameters before anything settles on-chain. The institution's capital never reaches a protocol that falls outside its approved parameters. That is the structural requirement that standard vault design does not meet.</p><h2 id="what-institutional-defi-infrastructure-is">What Institutional DeFi Infrastructure Is</h2><p>Institutional DeFi infrastructure is the set of technical and operational systems that enable regulated institutions to allocate capital into DeFi execution environments while maintaining custody integrity, mandate compliance, and audit capability throughout.</p><p>It differs from retail DeFi access in the same way that institutional staking differs from retail staking: not primarily in scale, but in operational architecture. A retail participant interacting with a DeFi vault accepts the vault curator's allocation decisions, assumes smart contract risk directly, and has no mechanism for enforcing mandate constraints at the transaction level. An institutional participant requires something structurally different.</p><p>The institutional requirement has four dimensions.</p><h3 id="custody-integrity">Custody integrity</h3><p>Capital must remain under the institution's control throughout the allocation lifecycle. Assets are not transferred to a vault operator, a curator, or an infrastructure provider. Delegation happens at the protocol level, and the institution retains withdrawal authority.</p><h3 id="mandate-compliance">Mandate compliance</h3><p>Every transaction must be validated against the institution's mandate parameters before execution. Concentration limits, protocol allowlists, counterparty restrictions, slippage thresholds, and oracle integrity requirements must all be enforced at the infrastructure layer, not left to the discretion of a vault curator.</p><h3 id="audit-capability">Audit capability</h3><p>The institution must be able to produce a complete, timestamped record of every transaction, every allocation decision, and every mandate validation event for accounting, tax reporting, compliance review, and audit purposes.</p><h3 id="governance-separation">Governance separation</h3><p>The entity operating the infrastructure must be independent of the entity making allocation decisions. When both functions are controlled by the same party, the institution has no structural protection against allocation decisions that optimise for the operator's interests rather than the institution's mandate.</p><p>These four requirements define what institutional DeFi infrastructure must deliver. Standard DeFi vault architecture does not deliver any of them by design.</p><h2 id="why-standard-defi-vault-architecture-falls-short">Why Standard DeFi Vault Architecture Falls Short</h2><p>Most DeFi vaults were built for a different capital profile. The governance assumptions, custody models, and reporting capabilities that exist in standard vault architecture reflect the requirements of retail participants, not regulated institutions.</p><h3 id="the-curators-discretion-problem">The curator's discretion problem</h3><p>Standard DeFi vaults delegate allocation authority to a curator. The curator decides which protocols receive capital, in what concentrations, and when. The institution has no mechanism to constrain that discretion against its own mandate parameters. If the curator routes capital to a protocol outside the institution's approved list or builds a concentration that exceeds the institution's risk limits, the institution has no structural protection. It can only exist after the fact.</p><h3 id="the-conflict-of-interest-problem">The conflict of interest problem</h3><p>Many vault operators are also protocol participants, liquidity providers, or token holders in the protocols to which they are allocated. The incentive structure that governs allocation decisions is not necessarily aligned with the institution's mandate. Routing that optimises for TVL, fee capture, or token appreciation can conflict directly with mandate alignment. DeFi displaces the institutional compliance infrastructure that has historically ensured transparency, accountability, and stability. By diffusing core intermediary functions across technical systems and human actors, DeFi introduces anonymity, regulatory arbitrage, and systemic risk.</p><h3 id="the-reporting-gap">The reporting gap</h3><p>Institutional accounting requires validator-level attribution, timestamped transaction records, and data in formats compatible with back-office systems. Standard vault products do not produce this data. They produce on-chain records that require significant post-processing to become usable for institutional reporting purposes.</p><h3 id="the-regulatory-compliance-gap">The regulatory compliance gap</h3><p>DeFi compliance is no longer just an idea — it is a requirement for any project that wants to attract large-scale investment. Global regulators have moved from watching the market to actively enforcing rules, with FATF updating its global standards and MiCA introducing obligations for identifiable governance bodies, foundations, and token issuers. Standard vault architecture was not designed to accommodate these requirements. The compliance gap is not cosmetic. It is the reason most institutional DeFi allocations never clear internal approval.</p><h2 id="what-the-protection-layer-is">What the Protection Layer Is</h2><p>The protection layer is the infrastructure component that sits between the institution's capital and DeFi execution environments. It is independent of the vault curators who manage allocation strategies. Its function is to validate every transaction against mandate parameters before anything settles on-chain.</p><figure class="kg-card kg-image-card kg-card-hascaption"><img src="https://p2p.org/economy/content/images/2026/05/p2p-institutional-defi-execution-stack.jpg" class="kg-image" alt="A three-layer horizontal diagram showing the institutional DeFi execution stack. On the left, the Institution block contains capital, mandate parameters, withdrawal authority, and audit review. In the centre, the Protection Layer block contains mandate validation, protocol allowlist, concentration limits, oracle integrity, slippage thresholds, and compliance record. On the right, the DeFi Execution block contains approved protocols, on-chain settlement, yield distribution, and supported protocols. Arrows between blocks show mandate parameters flowing right and audit trail returning left, with validated transactions only flowing from the protection layer to DeFi execution." loading="lazy" width="1600" height="900" srcset="https://p2p.org/economy/content/images/size/w600/2026/05/p2p-institutional-defi-execution-stack.jpg 600w, https://p2p.org/economy/content/images/size/w1000/2026/05/p2p-institutional-defi-execution-stack.jpg 1000w, https://p2p.org/economy/content/images/2026/05/p2p-institutional-defi-execution-stack.jpg 1600w" sizes="(min-width: 720px) 720px"><figcaption><i><em class="italic" style="white-space: pre-wrap;">The institutional DeFi execution stack. The protection layer sits between the institution and DeFi execution environments, validating every transaction against mandate parameters before anything settles on-chain.</em></i></figcaption></figure><p>The protection layer operates at the transaction level. Before capital is routed to any protocol, the protection layer checks:</p><ul><li>Is this protocol on the institution's approved allowlist?</li><li>Does this allocation create a concentration that exceeds the institution's limits?</li><li>Is the oracle providing price data for this transaction reliable and within acceptable parameters?</li><li>Does the slippage on this transaction fall within the institution's approved threshold?</li><li>Does this transaction comply with the institution's counterparty and jurisdiction restrictions?</li></ul><p>If any check fails, the transaction does not execute. The institution's capital does not reach a protocol that falls outside its approved parameters. This is mandate validation at execution, and it is the structural requirement that distinguishes institutional DeFi infrastructure from standard vault products.</p><p>The protection layer's independence from the curator is not an operational detail. It is the architectural requirement. An operator that controls both the protection layer and the allocation strategy has the ability to modify or bypass mandate validation in ways that benefit the allocation strategy. Institutional compliance frameworks require that these functions be held by separate, independent entities.</p><p><a href="http://p2p.org/?ref=p2p.org">P2P.org</a> operates the protection layer independently of vault curators. Our infrastructure validates transactions against institutional mandate parameters before execution, without discretion over allocation strategy. The curator allocates. The protection layer validates. The institution controls withdrawal authority throughout.</p><h2 id="the-risk-categories-specific-to-institutional-defi">The Risk Categories Specific to Institutional DeFi</h2><p>Institutional DeFi participation carries a risk profile that is distinct from both traditional asset management and from institutional staking. Each category requires explicit assessment before any program is designed.</p><h3 id="smart-contract-risk">Smart contract risk</h3><p>DeFi protocols operate on smart contracts. A vulnerability in a smart contract can result in loss of capital without the intervention of any human actor. Smart contract risk exists at the protocol layer and cannot be eliminated, only managed through protocol selection, concentration limits, and allowlist governance. This risk does not exist in native staking at the protocol layer.</p><h3 id="curator-risk">Curator risk</h3><p>In any vault arrangement, the institution is exposed to the decisions of the party controlling allocation. Curator risk includes misalignment of incentives, allocation to unapproved protocols, conflict of interest in routing decisions, and operational failure. The protection layer addresses curator risk at the transaction level by validating allocations against mandate parameters before execution, but it does not eliminate the underlying incentive misalignment that curator models create.</p><h3 id="oracle-risk">Oracle risk</h3><p>DeFi protocols rely on price oracles to determine collateralisation ratios, liquidation thresholds, and yield calculations. An oracle failure or manipulation event can cause unexpected liquidations or incorrect valuations. Institutional DeFi infrastructure must include oracle integrity checks as part of the mandate validation stack.</p><h3 id="liquidity-risk">Liquidity risk</h3><p>Capital deployed into DeFi vaults may be subject to lock-up periods, withdrawal queues, or liquidity constraints that restrict access during market stress. For institutions managing redemption obligations or treasury mandates, the liquidity profile of any DeFi allocation must be explicitly assessed and integrated into the institution's liquidity management framework.</p><h3 id="regulatory-and-compliance-risk">Regulatory and compliance risk</h3><p>Regulators across the world, including in the US and EU, are exploring how AML laws apply to DeFi platforms, which often operate in a grey area. This could mean integrating compliance-friendly mechanisms such as on-chain identity attestations. DeFi firms will likely need to prepare for the same-risk, same-rule enforcement across decentralised networks. Institutions operating across multiple jurisdictions must assess the compliance requirements for each operating market before deploying capital.</p><h3 id="concentration-risk">Concentration risk</h3><p>Unmanaged concentration in a single protocol, chain, or asset type creates exposure to correlated failure events. Institutional mandate parameters typically include explicit concentration limits. Enforcing those limits at the transaction level, before execution, is an infrastructure requirement.</p><h2 id="how-mandate-validation-works-at-the-transaction-level">How Mandate Validation Works at the Transaction Level</h2><p>Mandate validation is the process by which each transaction is checked against a defined set of institutional parameters before it executes on-chain. It is not a post-trade review. It is a pre-execution gate.</p><p>The mandate parameters an institution defines typically include:</p><ul><li>Protocol allowlist: the set of protocols the institution has approved for capital allocation</li><li>Concentration limits: maximum exposure to any single protocol, chain, or asset</li><li>Counterparty restrictions: jurisdictional or entity-level restrictions on protocol interaction</li><li>Oracle parameters: acceptable price sources and deviation thresholds</li><li>Slippage limits: maximum acceptable execution slippage per transaction type</li><li>Liquidity thresholds: minimum liquidity requirements for any protocol receiving allocation</li></ul><p>When a vault curator generates an allocation instruction, the protection layer checks the instruction against each parameter in the mandate. A transaction that passes all checks executes. A transaction that fails any check does not execute and generates a compliance record documenting the failure and the parameter it violated.</p><p>This architecture means the institution does not need to trust the curator's judgment on mandate compliance. The mandate is enforced mechanically, at the infrastructure layer, before capital moves. The audit trail produced by the validation process is available for compliance review, internal reporting, and external audit.</p><p>For a detailed technical explanation of how mandate validation operates in <a href="http://p2p.org/?ref=p2p.org">P2P.org</a>'s infrastructure, see: <a href="https://p2p.org/economy/defi-vaults-institutional-risk-tolerance/">Mandate Validation at Execution: What It Means for Regulated Allocators</a></p><h2 id="what-compliance-infrastructure-defi-allocations-require">What Compliance Infrastructure DeFi Allocations Require</h2><p>Institutional DeFi allocations require a compliance infrastructure that standard vault products do not provide. The gap is not primarily regulatory interpretation. It is operational capability.</p><h3 id="transaction-level-audit-trails">Transaction-level audit trails</h3><p>Every allocation instruction, every validation event, every execution outcome, and every failed mandate check must be captured in a timestamped, tamper-evident record. This record must be producible on demand for internal compliance review, external audit, and regulatory examination.</p><h3 id="role-separation-and-access-controls">Role separation and access controls</h3><p>The institution must be able to define and enforce separation between the parties with authority to set mandate parameters, the parties with authority to generate allocation instructions, and the parties with authority to operate the validation infrastructure. These roles must be documented and auditable.</p><h3 id="reporting-compatibility">Reporting compatibility</h3><p>Reward and yield attribution must be available at the transaction level and in formats compatible with institutional accounting and tax reporting systems. Protocol-level aggregates are not sufficient for institutional purposes.</p><h3 id="regulatory-reporting-capability">Regulatory reporting capability</h3><p>As DeFi compliance requirements evolve under MiCA, FATF guidance, and emerging US frameworks, the infrastructure must be capable of producing the reporting that regulatory obligations require. Institutions should assess whether their infrastructure provider has the capability to adapt reporting to new regulatory requirements without requiring architectural changes.</p><p>SOC 2 Type II certification, achieved by <a href="http://p2p.org/?ref=p2p.org">P2P.org</a> in December 2025, independently validates the operational controls governing the infrastructure layer, including availability, security, and the integrity of the audit trail.</p><h2 id="where-p2porg-sits-in-this-architecture">Where P2P.org Sits in This Architecture</h2><p>P2P.org builds the protection layer that sits between regulated institutions and DeFi execution environments, independently of the curators who manage allocation strategies.</p><p>Our infrastructure validates every transaction against institutional mandate parameters before execution. We do not manage the allocation strategy. We do not hold client assets. We do not participate in the protocols that our infrastructure routes capital to. Our role is to ensure that capital allocated through our infrastructure only reaches protocols that the institution has approved, under the conditions the institution has defined.</p><p>Across the DeFi Infrastructure for Institutions series, we explain each component of this architecture in detail: why standard vault design creates the curator conflict, how mandate validation operates at the transaction level, and what the compliance infrastructure for a regulated DeFi program looks like in practice.</p><p>If you are evaluating the infrastructure requirements for a DeFi allocation program, <a href="https://p2p.org/?ref=p2p.org#form" rel="noreferrer">reach out to our team</a>.</p><h2 id="due-diligence-checklist-evaluating-institutional-defi-infrastructure">Due Diligence Checklist: Evaluating Institutional DeFi Infrastructure</h2><p>For institutions evaluating infrastructure providers or initiating a DeFi allocation program, these are the foundational questions to answer before committing capital.</p><h3 id="custody-and-control">Custody and control</h3><p>[ ] Does the infrastructure provider hold client assets at any point in the allocation lifecycle? </p><p>[ ] Does the institution retain withdrawal authority throughout? </p><p>[ ] Is the custody model non-custodial, and is that independently documented?</p><h3 id="mandate-validation">Mandate validation</h3><p>[ ] Does the infrastructure validate transactions against mandate parameters before execution, or only after? </p><p>[ ] Can the institution define and modify its own mandate parameters independently of the infrastructure provider? </p><p>[ ] Is the validation logic documented, auditable, and independent of the allocation strategy?</p><h3 id="protection-layer-independence">Protection layer independence</h3><p>[ ] Is the infrastructure provider independent of the vault curators managing allocation strategy? </p><p>[ ] Does the provider have any financial interest in the protocols it routes capital to? </p><p>[ ] Is there a documented governance separation between infrastructure operation and allocation decisions?</p><h3 id="compliance-and-reporting">Compliance and reporting</h3><p>[ ] Does the infrastructure produce transaction-level audit trails compatible with institutional reporting requirements? </p><p>[ ] Can the provider deliver reporting in formats compatible with the institution's accounting and tax systems? </p><p>[ ] Does the provider hold SOC 2 Type II or equivalent independent certification?</p><h3 id="risk-controls">Risk controls</h3><p>[ ] Does the infrastructure enforce protocol allowlists, concentration limits, and oracle integrity checks at the transaction level? </p><p>[ ] What is the documented process for updating mandate parameters in response to new protocol approvals or risk events? </p><p>[ ] How does the provider handle oracle failure or protocol-level incidents?</p><h3 id="regulatory-capability">Regulatory capability</h3><p>[ ] Is the provider capable of adapting compliance reporting to new regulatory requirements without architectural changes? </p><p>[ ] Does the provider have documented AML and KYC procedures relevant to institutional DeFi operations? </p><p>[ ] Has the provider's infrastructure been reviewed or assessed by external legal or compliance advisors?</p><h2 id="key-takeaway">Key Takeaway</h2><p>Institutional DeFi infrastructure is the execution layer that makes on-chain capital allocation viable for regulated institutions. It enforces mandate compliance at the transaction level, maintains custody integrity throughout the allocation lifecycle, produces the audit trail that compliance and reporting require, and operates independently of the curators who manage allocation strategy.</p><p>The protocols have matured. The regulatory environment is clarifying. The infrastructure to connect regulated capital to DeFi execution environments now exists. The institutions building compliant DeFi allocation programs today are establishing the operational foundation for a category that will define how regulated capital participates in on-chain markets for the next decade.</p><p>Network conditions and protocol yields are variable. P2P.org does not control or set DeFi yield rates. Smart contract risks are protocol-defined and client-borne. Operational safeguards are implemented to reduce exposure, but do not eliminate protocol-level risk.</p><h2 id="frequently-asked-questions-faqs">Frequently Asked Questions (FAQs)<br></h2><h3 id="what-is-institutional-defi-infrastructure">What is institutional DeFi infrastructure?</h3><p>Institutional DeFi infrastructure is the set of technical and operational systems that enable regulated institutions to allocate capital into DeFi execution environments while maintaining custody integrity, mandate compliance, and audit capability throughout. It includes the protection layer that validates transactions before execution, the audit trail infrastructure that captures compliance records, and the governance architecture that separates infrastructure operation from allocation strategy. It is distinct from standard DeFi vault products, which were designed for retail capital and do not deliver the mandate validation, custody integrity, or reporting capability that regulated institutions require.</p><h3 id="what-is-the-protection-layer">What is the protection layer?</h3><p>The protection layer is the infrastructure component that sits between the institution's capital and DeFi execution environments. It validates every transaction against the institution's mandate parameters before anything settles on-chain. If a transaction would route capital to an unapproved protocol, breach a concentration limit, fail an oracle integrity check, or exceed a slippage threshold, the transaction does not execute. The protection layer operates independently of vault curators and does not have discretion over allocation strategy. Its function is mandate enforcement at the transaction level.</p><h3 id="why-do-standard-defi-vaults-fall-short-for-institutions">Why do standard DeFi vaults fall short for institutions?</h3><p>Standard DeFi vaults delegate allocation authority to a curator without providing the institution any mechanism to constrain that discretion against its own mandate parameters. The curator decides which protocols receive capital, in what concentrations, and when. The institution has no structural protection against allocations that fall outside its mandate. Standard vaults also do not produce the transaction-level audit trails that institutional reporting requires, and their governance architecture does not separate the infrastructure operator from the allocation strategy, creating the conditions for curator conflict of interest.</p><h3 id="what-risks-are-specific-to-institutional-defi-participation">What risks are specific to institutional DeFi participation?</h3><p>The primary risk categories are smart contract risk (protocol-level code vulnerabilities), curator risk (misaligned incentives in allocation decisions), oracle risk (price feed failures or manipulation), liquidity risk (lock-up periods or withdrawal constraints), regulatory and compliance risk (varying treatment across jurisdictions), and concentration risk (unmanaged exposure to correlated failure events). Each category requires explicit assessment and mitigation as part of any institutional DeFi program design. The protection layer addresses mandate validation and concentration risk at the transaction level, but does not eliminate smart contract risk or underlying curator incentive misalignment.</p><h3 id="what-does-mandate-validation-at-execution-mean">What does mandate validation at execution mean?</h3><p>Mandate validation at execution means that every transaction is checked against a defined set of institutional parameters before it executes on-chain. The parameters typically include a protocol allowlist, concentration limits, counterparty restrictions, oracle integrity thresholds, slippage limits, and liquidity requirements. A transaction that passes all checks executes. A transaction that fails any check does not execute and generates a compliance record. This is a pre-execution gate, not a post-trade review. It means the institution does not rely on the curator's judgment for mandate compliance. The mandate is enforced mechanically at the infrastructure layer before capital moves.</p><h3 id="what-compliance-infrastructure-does-a-defi-allocation-require">What compliance infrastructure does a DeFi allocation require?</h3><p>Institutional DeFi allocations require transaction-level audit trails, role separation between mandate governance and allocation execution, reporting compatibility with institutional accounting and tax systems, and the capability to adapt to evolving regulatory requirements. The infrastructure provider should hold independent certification such as SOC 2 Type II, which validates that operational controls governing availability, security, and audit trail integrity are operating as documented. Institutions should assess whether their infrastructure provider can produce the compliance reporting their regulators require without requiring architectural changes to the infrastructure.</p><h3 id="what-is-the-difference-between-custodial-and-non-custodial-defi-infrastructure">What is the difference between custodial and non-custodial DeFi infrastructure?</h3><p>In non-custodial DeFi infrastructure, the institution's assets remain under the institution's control throughout the allocation lifecycle. The infrastructure provider operates the validation and execution layer but never holds the assets. Withdrawal authority remains with the institution. In custodial arrangements, assets are transferred to the infrastructure provider or a third-party custodian, which triggers additional regulatory obligations in most institutional compliance frameworks. Non-custodial architecture is the standard requirement for regulated institutions participating in DeFi, as it preserves custody integrity and avoids the regulatory implications of asset transfer.</p><hr><h3 id="about-p2porg">About <a href="http://p2p.org/?ref=p2p.org">P2P.org</a></h3><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">talk to our team</a>.</p><hr><h3 id="disclaimer">Disclaimer</h3><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>