Stake Now Contact Us
DORA ICT Third-Party Risk Checklist for Staking Providers

Institutional

DORA ICT Third-Party Risk Checklist for Staking Providers: What EU Financial Entities Should Verify

A DORA ICT third-party risk checklist for EU banks, CASPs and custodians: what to verify when considering a validator.

NOV 19, 2026

Last updated NOV 19, 2026 · V1

TL;DR

  • DORA typically treats validator operation for an EU financial entity as an ICT service under Articles 28 to 30.
  • The Register of Information typically records the provider, networks, node regions, hosting subcontractors and criticality, with a December 31 reference date.
  • Article 30 clauses could translate into uptime targets, incident help, node locations, subcontracted hosts, audit rights and exit support.
  • Exit plans may need to cover unbonding queues, client-held withdrawal credentials and migration without double signing.

Where Does Staking Infrastructure Fall Under DORA?

A staking provider that operates validators for an EU financial entity generally qualifies as an ICT third-party service provider under DORA. Article 3(21) defines ICT services as digital and data services delivered through ICT systems on an ongoing basis, which may cover node hosting, validator operation and remote signing.

DORA has applied since January 17, 2025 to the financial entities listed in Article 2, including:

  • crypto-asset service providers (CASPs) authorised under MiCA, including custodians that offer staking,
  • credit institutions that hold crypto-assets for clients,
  • MiFID II firms,
  • UCITS management companies and alternative fund managers (AIFMs).

Firms relying on the MiCA transitional period stayed outside DORA scope until CASP authorisation ended no later than July 1, 2026.

A critical or important function is one whose disruption would materially impair financial performance, service continuity or compliance with authorisation conditions. A validator outage or slashing event at a CASP offering staking may point toward that classification, which the financial entity typically documents under Delegated Regulation (EU) 2024/1773.

What Should the Register of Information Record for a Staking Provider?

The Register of Information typically records every ICT contract, staking included, in the templates of Implementing Regulation (EU) 2024/2956. For the 2026 cycle, the reference date was December 31, 2025, with CSSF submission due by March 31, 2026, while other authorities set similar windows.

Staking entries typically include:

  • Provider identity: legal entity, LEI or EUID, ultimate parent and country (B_05.01).
  • Service and regions: networks, validator setup, remote signer and node countries (B_02.01, B_02.02).
  • Hosting subcontractors: cloud and bare-metal hosts, ranked above 1 in the supply chain (B_05.02).
  • Criticality: the function supported and its classification (B_06.01).
  • Exit assessment: substitutability and replacement options (B_07.01).

Article 28(3) also typically requires timely notice to the competent authority of planned contracts for critical or important functions, which a new staking mandate might trigger.

Which Evidence Should EU Financial Entities Request Before Signing?

Before signing, the client typically collects independent evidence on the provider’s controls, keys and testing, since Delegated Regulation (EU) 2024/1773 may limit reliance on certifications and audit reports alone. The financial entity typically remains fully responsible under Article 28(1), so vendor self-attestation may leave the risk with the client.

The evidence pack may include:

  • a SOC 2 Type II report and an ISO/IEC 27001:2022 certificate whose scope names validator and signing systems,
  • an independent DORA controls assessment,
  • penetration test results from the last 12 months,
  • key management and remote-signer design showing how one key is prevented from signing on 2 hosts,
  • an incident procedure,
  • a documented exit procedure covering key migration with slashing prevention data.

Wider selection criteria and slashing controls are covered in the Everstake guide to choosing a staking provider and the Everstake guide to slashing prevention.

How Should EU Financial Entities Read a DORA Controls Assessment?

A DORA controls assessment is read for scope, timing, findings and subcontractor coverage before the client relies on it. Key checks include:

  • Scope: which DORA articles were assessed, compared with the client’s obligations under Articles 28 to 30.
  • Assessor and standard: who performed the review and under which audit standard, such as ISO 19011.
  • Timing: a point-in-time result typically shows control design, and a period result may also show operation.
  • Findings: exceptions, management responses and remediation dates.
  • Subcontractor coverage: where a host is carved out, the assessor typically did not examine its controls.
  • Client-side controls: controls the provider assumes its clients operate, such as custody of withdrawal credentials.

How Do Article 30 Contract Clauses Apply to Validator Operations?

Article 30(2) sets 9 minimum terms that typically apply to every ICT contract, and Article 30(3) adds 6 terms where services support critical or important functions. 

Article 30 clauseStaking equivalentWhat to verify
30(2)(a) Services and subcontractingNetworks, validators, remote signerEach network listed; hosting subcontracting position
30(2)(b) LocationsNode and signer regionsCountries per network; notice before relocation
30(2)(e), 30(3)(a) Service levelsUptime, attestation effectivenessTargets, data source, remedies
30(2)(f) Incident assistanceDowntime, slashing eventsResponse times and cost
30(3)(b) NoticeHost, client, key or ownership changesNotice long enough to object
30(3)(c) Contingency and securityFailover without double signingTested failover; slashing protection
30(3)(d) TLPTValidator and signer systemsClient TLPT
30(3)(e) Audit and accessNode and key operationsRights for client, appointee and authority
30(2)(h) TerminationSlashing, unapproved hostsTriggers under Article 28(7)
30(2)(d) Data at exitLogs, signing historyEIP-3076 export
30(3)(f) Exit and transitionUnbonding, key migrationTransition longer than unbonding

For subcontracted hosting, Delegated Regulation (EU) 2025/532 lists 12 contract conditions and may let the client object to material changes.

How Can an EU Financial Entity Exit a Staking Provider Without Disruption?

A staking exit plan typically accounts for protocol waiting periods, client control of withdrawal credentials in non-custodial staking and migration without double signing. Article 28(8) might require tested, periodically reviewed exit plans for critical or important functions, and Article 30(3)(f) a transition period that may need to exceed the longest unbonding window.

Protocol waiting periods set the minimum timeline:

  • Ethereum: a demand-driven exit queue, about 13 days and 8 hours on October 5, 2026, plus the withdrawal sweep.
  • Solana: one epoch, about 2 to 3 days.
  • Cosmos Hub: a fixed 21 days.

On Ethereum, client-held withdrawal credentials can trigger an exit without the provider’s signing key through EIP-7002, live since May 7, 2025. On Solana, stake accounts contain separate stake and withdraw permissions, so the client can keep withdraw authority.

Moving a signing key without unbonding risks slashing if 2 hosts sign at once, and EIP-3076 defines a format for carrying slashing protection history between clients.

An exit test may include:

  1. Trigger a small test exit and record elapsed time per network.
  2. Confirm that withdrawal credentials and withdraw authorities are client-controlled.
  3. Rehearse key migration with slashing protection data on a testnet.
  4. Record results in B_07.01 and report them to the management body.

What Is Typically Monitored and Reported After Signing?

After signing, the client typically monitors provider performance and reports major incidents within fixed deadlines, reviewing its contractual policy at least yearly. For a major ICT-related incident, the financial entity is typically required to file:

  1. an initial notification within 4 hours of classification and no later than 24 hours after awareness,
  2. an intermediate report within 72 hours of the initial notification,
  3. a final report within 1 month of the latest intermediate report.

Downtime over 2 hours for services supporting critical or important functions is one classification criterion, so a validator outage might start the 4-hour clock.

Ongoing monitoring may cover:

  • monthly uptime, attestation and slashing reports,
  • advance notice of host, region or key changes,
  • a yearly refresh of SOC 2 Type II, ISO/IEC 27001 and DORA evidence,
  • reporting to the management body.

DORA ICT Third-Party Risk Checklist for Staking Providers

The table gives vendor-risk, compliance and procurement teams one reference for staking due diligence and contract remediation.

RequirementDORA articleStaking-specific checkEvidence
Classify the functionArt. 3(22), 28(4)Outage or slashing effect on client servicesBusiness impact analysis
Due diligenceArt. 28(4), 2024/1773Controls over validators and signersSOC 2 Type II, ISO/IEC 27001, DORA assessment
Assessment reviewArt. 28(1)Scope, timing, findings, hosting coverageFull report; bridge letter if dated
Security and keysArt. 28(5), 30(2)(c)Penetration tests, remote signer, slashing protectionTest summary, architecture document
Register entryArt. 28(3), ITS 2024/2956Networks, regions, ranked hostsLEI, hosting and region lists
Service termsArt. 30(2)(a), (b), 30(3)(a)Uptime targets, node locations, subcontracted hostsSigned SLA, region and subcontractor lists
Oversight termsArt. 30(3)(d), (e), 2025/532Audit access, TLPT, host-change objectionsAudit and TLPT clauses, change process
ConcentrationArt. 29Stake per host, ASN and client softwareDistribution report per network
Incident supportArt. 19, 30(2)(f)Notice windows for downtime and slashingIncident procedure
Exit and terminationArt. 28(7), 28(8), 30(3)(f)Unbonding, withdrawal credentials, key migration, triggersTested exit plan, termination clause

Everstake’s DORA Controls Independent Assessment

Everstake is among the small set of companies who completed an independent assessment of its ICT controls against selected DORA requirements, which EU institutional clients can use in their own third-party risk reviews. Prescient Security performed the review under ISO 19011, with controls evaluated as of June 5, 2026.

DORA has no formal certification scheme, so Everstake describes the work as a completed controls assessment. It complements these Everstake attestations and certifications:

  • SOC 2 Type II,
  • ISO/IEC 27001:2022,
  • NIST CSF 2.0, assessed at a maturity score of 4.16,
  • GDPR and CCPA compliance.

Delivery options include Everstake Institutional Staking, Validator-as-a-Service (VaaS), and setups for custodians and exchanges and wallets.

Request the full assessment through the Everstake Trust Center, or talk to our Institutional Staking team about what your DORA review needs:

FAQ

Is a staking provider an ICT third-party service provider under DORA?

Yes, a provider that operates validators for an EU financial entity generally qualifies as an ICT third-party service provider.

Does staking support a critical or important function?

It may, depending on how a validator outage or slashing event would affect the financial entity’s services under the Article 3(22) test.

What should a staking provider contract include under Article 30?

It typically needs the 9 Article 30(2) terms and, for critical or important functions, the 6 Article 30(3) terms, including audit rights, TLPT and exit support.

How do unbonding periods affect a DORA exit plan?

They may set the minimum transition period: about 2 to 3 days on Solana, 21 days on Cosmos Hub and a demand-dependent queue on Ethereum.

Is a DORA certification available?

No, DORA has no formal certification scheme, so providers typically evidence alignment through independent assessments and attestations such as SOC 2 Type II.

This article is for information only and does not constitute legal advice.

Share with your network

Sign Up for
Our Newsletter

By submitting this form, you are acknowledging that you have read and agree to our Privacy Notice, which details how we collect and use your information.