Validator Due Diligence Framework. What Institutions Really Need to Evaluate.

Series: Validator Playbook | Institutional Infrastructure

The Validator Playbook is P2P.org's operational series for infrastructure engineers, staking product managers, and validator risk committees building or evaluating institutional-grade staking programs. Each article addresses a specific operational, technical, or governance dimension of running or selecting validator infrastructure at an institutional scale.

Previously in the series: Ethereum Slashing Explained: What Custodians, Funds and Exchanges Must Know

Learnings for Busy Readers

What this article covers:

• Why standard metrics like fees and uptime are insufficient for institutional due diligence
• The seven dimensions that institutional validator due diligence must cover
• The questions to ask at each stage and what good answers actually look like
• A complete due diligence checklist for procurement and risk committee use

The core argument: Validator due diligence is not a yield evaluation. It is an engineering reliability assessment. The institutions that make delegation decisions on the basis of mechanisms, not marketing, consistently achieve better outcomes across uptime, slashing avoidance, and incident response.

Introduction

Most validator due diligence processes start in the wrong place. Fee schedules get compared. Uptime dashboards get reviewed. Marketing materials get forwarded to risk committees. And then a delegation decision gets made on the basis of information that does not actually describe how a validator performs when something goes wrong.

In 2026, staking is no longer a peripheral activity for institutions. The institutional staking services market reached USD 5.8 billion in 2024 and is projected to grow to USD 33.31 billion by 2033 (Source: CoinShares). As allocations grow and staking becomes embedded in custody platforms, treasury programs, and regulated ETF products, the validator selection decision carries consequences that extend well beyond the immediate yield impact. A validator failure is an operational incident. A slashing event is a financial loss and potentially a regulatory disclosure obligation. Getting the selection process right is not optional.

This article sets out a practical due diligence framework for institutional teams evaluating validator infrastructure. It is written for staking product managers, validator risk committees, infrastructure engineers, and procurement teams who need to go beyond the surface metrics and understand what a validator operation actually looks like under stress.

Why Standard Metrics Are Not Enough

The most commonly referenced validator metrics are commission rate, advertised APY, and uptime percentage. None of these tells you what you actually need to know.

The commission rate tells you the price. It does not tell you what the price buys, whether the fee model is sustainable, or whether the operator has the resources to invest in the infrastructure quality that protects your stake. An aggressively low fee may be attractive in the short term, but it can also signal an under-resourced operation or a commercial strategy focused on volume rather than long-term relationships.

Advertised APY is a function of network conditions, not operator quality. Two validators on the same network with identical commission rates will produce similar yields under normal conditions. The difference between them shows up during chain upgrades, periods of network congestion, and incident response.

In 2026, the highest-impact staking outcomes are determined by operational reliability, key-management decisions, and incident behaviour, not the headline APR. The most expensive failures show up during chain upgrades, congestion, correlated cloud incidents, or governance-driven parameter changes (Source: Crypto Adventure).

Uptime percentage is the most misleading metric of all. A validator can show 99.9% average uptime across a reporting period while having failed catastrophically during the one critical window that mattered. A client upgrade weekend. A network fork. A period of unusual congestion. Average uptime hides the variance that institutional risk frameworks are designed to assess.

The right frame for validator due diligence is not a yield evaluation. It is an engineering reliability assessment conducted the same way a risk committee would assess any critical infrastructure vendor.

The Seven Dimensions of Institutional Validator Due Diligence

1. Infrastructure Architecture and Failure Mode Analysis

The first question is not where the infrastructure is located. It is how it's designed to fail.

Every validator infrastructure has failure modes. The relevant question is whether those failure modes are independent or correlated. A validator operation that runs all nodes in the same cloud region with the same automation pipeline and the same deployment tooling has correlated failure risk. A single incident, a regional outage, or a software bug in an automated update can take down the entire operation simultaneously.

Validator operations should be evaluated like reliability engineering. A buyer should focus on correlated failure and safe redundancy. Downtime can trigger penalties when validators fail to meet protocol participation requirements. More severe penalties can be triggered by unsafe redundancy that leads to double-signing (Source: Crypto Adventure).

The architecture questions that matter:

• Are nodes distributed across independent infrastructure providers and geographic regions?
• Are multiple consensus client implementations supported to reduce client diversity risk?
• Is there active-active or active-passive failover, and how does the failover logic prevent double-signing?
• What is the rollback procedure if a software update causes instability?
• Does the provider operate bare metal infrastructure, cloud, or a hybrid, and how is each maintained?

A mature operator can answer each of these questions with specifics. An operator competing primarily on price typically cannot.

2. Key Management and Access Controls

Validator key management is the most consequential security dimension in any staking program. A key compromise does not always result in direct theft of assets, but it can result in slashable behaviour, validator downtime, loss of governance participation, and reputational exposure that exceeds the financial loss.

In institutional staking, not all risk lies in infrastructure. It is also critical to understand who controls what: funds, signing keys, withdrawal credentials, reward parameters, exit processes, and operational authorisations. It is therefore not enough to speak abstractly about custodial or non-custodial staking. Due diligence must break down the operational and contractual flow: what the operator does, what the client retains, what the custodian controls, and which points require joint authorisation.

The key management questions that matter:

• Are signing keys and withdrawal keys held in separate environments with separate access controls?
• Are Hardware Security Modules (HSMs) used for signing key operations?
• How is access to signing infrastructure controlled, logged, and audited?
• What is the procedure for key rotation, and how is it tested?
• How is double-signing prevented specifically during failover events?

Institutions should request a written description of the key management architecture, not a verbal summary. The document should specify who holds what access, under what conditions access is granted, and how key operations are logged.

3. Slashing Risk Controls and Incident History

Slashing is the protocol-level penalty for validator misbehaviour. The two primary causes are double-signing and prolonged inactivity. Both are largely preventable through good operational design. For a detailed breakdown of how Ethereum's slashing mechanics work at the protocol level, refer to the previous article in this series: Ethereum Slashing Explained: What Custodians, Funds and Exchanges Must Know.

For institutional due diligence, the relevant questions are not whether slashing has occurred, but what the operator's controls are, whether those controls have been tested, and what happened in any historical incidents.

The slashing risk questions that matter:

• What technical controls prevent double-signing during failover events specifically?
• Has the operator experienced any slashing events? What was the root cause, and what architectural changes followed?
• How are slashing conditions monitored in real time?
• What is the incident response procedure if a slashing risk is detected before it triggers?
• What contractual coverage applies to slashing losses, and what are the specific exclusions?

Be precise about slashing guarantee language. Whether slashing guarantees exist and what exclusions apply is a critical evaluation question. The due diligence question is not whether these words exist on a page, but how they map to reality: how keys are protected, how changes are approved, what happens in incident response, and what financial or contractual backstops exist (Source: Crypto Adventure).

4. Change Management and Protocol Upgrade Handling

Protocol upgrades are one of the highest-risk moments in any validator operation. Client software must be updated within specific windows. Timing matters. Rollback procedures must be available. Governance decisions must be understood and acted on promptly.

Institutions that delegate to validators are, in effect, delegating the decision of how protocol upgrades are handled. That is a governance decision with direct financial consequences, and it requires explicit evaluation.

The upgrade management questions that matter:

• How does the operator track protocol upgrade schedules across the networks it validates?
• What is the process for testing upgrades before deploying to production validators?
• How are staged rollouts managed, and what triggers a rollback?
• Does the operator participate in validator governance processes, and is there a documented policy?
• How are clients notified of upcoming upgrades and their potential operational impact?

5. Reporting and Auditability

Institutional staking programs require reward attribution at the validator level, in formats compatible with internal risk management systems and external audit requirements. A dashboard is a monitoring infrastructure. An audit trail is something different.

A buyer should request sample reporting packs that mirror internal requirements, including reward timing granularity and event classification, clear separation of principal, rewards, and fees, and chain event treatment such as redelegations or downtime penalties.

The reporting questions that matter:

• Can the provider deliver reward attribution at the validator level, disaggregated by epoch and by asset?
• Is the reporting format compatible with internal accounting and risk management systems?
• Is there an exportable, independently verifiable audit log of all validator operations, not just a dashboard?
• How are chain events such as downtime penalties, redelegations, and slashing incidents logged and reported?
• Can reporting be delivered in formats required for tax reporting in the institution's operating jurisdiction?

On certifications: SOC 2 Type II is the most relevant independent security attestation for validator infrastructure providers. Enterprise clients typically want Type II reports because they demonstrate how controls perform in real operations, not just at a point in time (Source: Wolfia). A SOC 2 Type II report covering availability and security criteria provides meaningful independent assurance that the controls governing validator uptime and key management are operating as documented. It is a floor, not a ceiling, but it is a meaningful one. P2P.org achieved SOC 2 Type II certification in December 2025, independently validating our operational controls across security and availability criteria.

6. Commercial Terms, SLAs, and Exit Procedures

The commercial structure of a staking relationship defines the accountability framework. Fees, SLAs, and exit procedures are not administrative details. They are the contractual expression of how risk is allocated between the institution and the provider.

SLAs should specify response times, escalation paths, penalties if uptime falls below the guarantee, and custom agreements. The question is what support is included: 24/7 monitoring, dedicated account teams, reporting, incident management, custodian integrations, contractual coverage, and contingency response capability.

The commercial terms questions that matter:

• What is the fee structure, and what is explicitly included vs. billed as an add-on?
• Are there different tiers for standard delegation versus dedicated validator operations?
• What does the SLA actually commit to, and what are the remedies if commitments are not met?
• What is the procedure for migrating stake to a different provider if the relationship ends?
• What would happen operationally if the provider ceased operations, and is there a documented continuity plan?

It is also important to review exit processes: migration, validator changes, and orderly off-boarding. Another useful question is what would happen if the provider ceased operations tomorrow. The quality of the answer often reveals its maturity.

7. Protocol Coverage and Multi-Chain Operational Consistency

Institutional staking programs increasingly span multiple proof-of-stake networks. Ethereum, Solana, Polkadot, Cosmos, and others each have distinct consensus mechanisms, upgrade cycles, slashing conditions, and governance processes. A provider that operates well on Ethereum may not have the same operational maturity on Solana.

The protocol coverage questions that matter:

• On which networks does the provider have the deepest operational track record?
• Are the infrastructure, architecture, and key management controls consistent across all supported networks?
• How does the provider handle networks with different upgrade cadences and governance participation requirements?
• Is there chain-specific reporting available for each network in the institution's portfolio?
• How many networks does the provider support, and is that breadth matched by operational depth?

P2P.org operates non-custodial validator infrastructure across more than 40 proof-of-stake networks, with consistent operational standards applied across each. Our Solana staking infrastructure and Ethereum staking infrastructure pages describe the specific architecture and reporting capabilities for each network, and our technical documentation provides integration details for procurement and engineering teams.

Evaluating validator infrastructure for your institution? P2P.org provides non-custodial staking across 40+ proof-of-stake networks with SOC 2 Type II certified operational controls, validator-level reporting, and dedicated institutional support. Explore P2P.org Staking Infrastructure

Due Diligence Checklist

For staking product managers, validator risk committees, and procurement teams conducting institutional validator due diligence. Organised by the seven dimensions covered above.

Infrastructure architecture: [ ] Nodes distributed across independent infrastructure providers and geographic regions [ ] Multiple consensus client implementations supported to reduce client diversity risk [ ] Failover logic documented and specifically designed to prevent double-signing [ ] Rollback procedures exist and have been tested for software update failures [ ] Infrastructure type (bare metal, cloud, hybrid) documented with maintenance procedures

Key management: [ ] Signing keys and withdrawal keys held in separate environments with separate access controls [ ] HSM or equivalent used for signing key operations [ ] Access to signing infrastructure is logged, audited, and role-based [ ] Key rotation procedures are documented and tested [ ] Double-signing prevention mechanism specifically covers failover scenarios

Slashing risk controls: [ ] Technical controls against double-signing during failover are documented [ ] Slashing incident history reviewed, including root cause and architectural changes [ ] Real-time slashing condition monitoring is in place with defined alerting [ ] Incident response procedure for pre-slashing detection is documented [ ] Slashing guarantee or coverage language reviewed with specific exclusions confirmed

Change management: [ ] Protocol upgrade tracking process documented for all supported networks [ ] Staged rollout and rollback procedures for software updates are in place [ ] Governance participation policy is documented [ ] Client notification process for upgrades is defined with timelines

Reporting and auditability: [ ] Validator-level reward attribution available disaggregated by epoch and asset [ ] Reporting format compatible with internal accounting and risk management systems [ ] Exportable audit log of all validator operations available (not dashboard only) [ ] Chain event treatment (downtime, redelegations, slashing) is logged and reportable [ ] SOC 2 Type II report available covering security and availability criteria

Commercial terms: [ ] Fee structure reviewed with explicit list of included vs. additional services [ ] SLA reviewed with specific uptime commitments and remedies confirmed [ ] Exit and migration procedure documented [ ] Operational continuity plan reviewed for provider cessation scenario

Protocol coverage: [ ] Operational track record reviewed on each specific network in the institution's portfolio [ ] Infrastructure and key management controls confirmed as consistent across networks [ ] Chain-specific reporting confirmed as available for each required network [ ] Governance participation policy confirmed for each relevant network

Key Takeaway

Validator due diligence is a reliability engineering assessment. The institutions that treat it as a yield comparison consistently underperform relative to those that evaluate mechanisms: how the infrastructure is designed to fail safely, how keys are managed and protected, how slashing is prevented rather than just insured against, and how the provider behaves when something goes wrong.

The seven dimensions covered in this framework are not equally weighted. Infrastructure architecture and key management are foundational. Slashing history and controls are the clearest signals of operational maturity. Reporting and audit trail capability determine whether the program can survive internal compliance scrutiny. Commercial terms and exit procedures define accountability. Protocol coverage determines whether the relationship can grow with the institution's staking program.

Evaluate each dimension with evidence, not assertions. Request documentation, ask for incident histories, and treat the quality of answers as a signal in itself.

FAQ

What is validator due diligence?

Validator due diligence is the process of evaluating a proof-of-stake validator infrastructure provider before delegating institutional capital. It covers infrastructure architecture, key management, slashing risk controls, change management, reporting capabilities, commercial terms, and protocol coverage. It is distinct from a yield evaluation and should be conducted as a reliability engineering assessment.

Why are uptime percentages insufficient for institutional due diligence?

Average uptime percentages hide variance. A validator can achieve 99.9% average uptime while failing critically during the specific high-risk windows that matter most, such as client upgrades, network forks, or congestion events. Institutional risk frameworks require understanding incident behaviour and failure mode design, not average performance under normal conditions.

What is the most important dimension of validator due diligence?

Infrastructure architecture and key management are the foundational dimensions. Slashing history and controls are the clearest signals of operational maturity. No single dimension is sufficient on its own. A provider with excellent infrastructure but opaque key management or no documented incident response is not a complete institutional partner.

What certifications should an institutional staking provider have?

SOC 2 Type II is the most relevant independent security attestation for validator infrastructure providers. It independently verifies that operational controls governing uptime and security are operating as documented over a sustained period, not just at a point in time. ISO 27001 is an additional signal of information security management maturity. Certifications are a floor, not a ceiling, and should be reviewed alongside the specific controls they cover.

How should institutions evaluate slashing guarantees offered by providers?

Slashing guarantee language requires careful examination. The relevant questions are not whether the guarantee exists but what the specific exclusions are, what the maximum coverage is, and how the guarantee maps to the provider's actual controls. A guarantee that excludes the most likely slashing causes, such as misconfigurations during upgrades, provides limited protection. The strongest protection comes from robust anti-slashing controls, not contractual language.

What should the exit and migration procedures include?

Exit and migration procedures should document how stake is transferred to a new provider without exposing the institution to unnecessary downtime or slashing risk during the transition, who is responsible for each step, what the expected timeline is for each network, and what happens to accumulated rewards during the migration. Institutions should test the provider's fluency with this question during initial evaluation. A provider who cannot answer clearly has not thought through the scenario.

How does validator due diligence differ across proof-of-stake networks?

Each proof-of-stake network has distinct consensus mechanisms, upgrade cadences, slashing conditions, and governance processes. Validator due diligence must be conducted on a network-by-network basis, not generalised across a provider's entire portfolio. A provider with deep operational experience on Ethereum may have more limited maturity on Solana or Polkadot. Request chain-specific incident history and performance evidence for each network in the institution's staking program.

Get Advise

Protocol-generated rewards are determined by network conditions and are variable. P2P.org does not control or set reward rates. Slashing risks are protocol-defined and client-borne. Operational safeguards are implemented to reduce slashing exposure, but do not eliminate protocol-level risk.

Disclaimer

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.