Crypto Staking Under MiCA 2026 — Service, Custody or Out of Scope

The structural question

Staking is the activity of using crypto-asset holdings to participate in Proof-of-Stake (PoS) consensus mechanisms — the user locks up tokens, runs (or delegates to) validators, earns rewards. Whether staking falls within MiCA scope depends entirely on the operational structure. Three main patterns:

Pattern 1 — User self-staking. The user controls the private keys, runs the validator software (or uses a self-hosted setup), and receives rewards directly. No CASP involvement. Out of scope under MiCA Article 2(2)(e) — the DeFi carve-out for fully decentralised activity without intermediary.

Pattern 2 — CASP staking-as-a-service. A CASP custodies the user’s crypto-assets and operates the staking infrastructure on behalf of the user. The CASP is the intermediary. In scope of MiCA: at minimum, custody and administration of crypto-assets (Article 3(1)(17)) plus typically transfer of crypto-assets and operational management of the staking activity.

Pattern 3 — Delegated staking through CASP. The CASP custodies the user’s crypto-assets and delegates them to external validators. The user receives the rewards via the CASP. In scope on the same basis as Pattern 2 — custody plus delegation service.

For the user, all three patterns may produce similar economic outcomes. For the CASP and the supervisor, the regulatory treatment is materially different.

What ESMA’s Q&A clarifies

ESMA’s 2025-2026 Q&A on MiCA addressed staking-treatment ambiguities. The key clarifications:

Custody of staked assets is custody. Where a CASP holds staked client crypto-assets, the custody framework under Article 75 applies. Segregation, daily reconciliation, bankruptcy-remoteness — all required for staked assets the same as for non-staked.

Operating staking infrastructure is a separate service consideration. The CASP may need to consider whether operating staking-infrastructure (running validators, managing keys, optimising rewards) constitutes a separate Article 3 service. ESMA Guidelines treat this as an integrated part of the custody-administration service where conducted on behalf of clients.

Reward distribution is part of the service. Where the CASP distributes staking rewards to client accounts, that activity is part of the staking-as-a-service offering — covered by the broader custody and administration framework.

Slashing risk allocation defaults to the CASP. Article 75(7) loss-compensation framework allocates slashing losses to the CASP unless properly documented as user-allocated. Most CASP staking services bear slashing risk and document it in service terms.

Liquid staking — a separate classification

Liquid staking is the practice of issuing a tokenised representation of staked crypto-assets that can be transferred and used in DeFi while the underlying assets remain staked. Examples: stETH (Lido), mSOL (Marinade), rETH (Rocket Pool).

Liquid staking raises a distinct classification puzzle:

The liquid-staking token itself. Issued by an identifiable issuer or by smart contracts. Falls within MiCA Title II as a generic crypto-asset, or potentially Title III as an ART if the token design tracks the underlying asset value through a stabilisation mechanism rather than pure 1:1 representation. ESMA case-by-case classification.

The issuance entity. If a legal entity issues the liquid-staking token (whether centralised like Lido DAO’s stETH or institutional like Coinbase’s cbETH), that entity is the issuer under MiCA. Title II white-paper notification or Title III/IV authorisation applies.

The liquid-staking activity itself. If the issuer custodies the underlying staked assets on behalf of token holders, that’s a CASP custody service. The combination of token issuance and custody service produces a layered regulatory picture.

Liquid staking products operating in the EU through 2026 have generally either:

• Sought MiCA Title II treatment for the liquid-staking token plus CASP authorisation for the custody service, or
• Relied on the Article 2(2)(e) DeFi carve-out where the project genuinely lacks identifiable issuer/operator (rare in practice)

The 2026 ESMA review under MiCA Article 142 will likely produce sharper guidance on liquid staking classification.

The substantive obligations for CASP staking-as-a-service

CASPs offering staking-as-a-service face the full conduct stack:

Article 75 custody safeguarding. Segregation of staked client crypto-assets from CASP own assets and from other clients’ assets. Daily reconciliation. Bankruptcy-remoteness. Sub-custody rules where validators are operated by third parties.

Article 7 marketing communications. Risk disclosures including slashing risk, lock-up periods, validator-selection criteria, reward variability. ESMA Guidelines on format-specific risk warnings apply.

Article 67 own funds. No specific increase for staking activity but the operational risk profile may inform the prudential assessment under Article 68 governance.

Article 73 outsourcing. Where validator operations are outsourced to third parties, the outsourcing framework applies including service-level monitoring, sub-custody chain documentation.

Article 78 inducements. Where validator selection is influenced by third-party arrangements (MEV revenue sharing, priority slot allocation), the inducements rule may apply.

The slashing risk question

Slashing is the protocol penalty for validator misbehaviour or extended downtime. Typical slashing scenarios:

• Validator double-signs (proposes conflicting blocks) — material slashing
• Validator goes offline for extended periods — small slashing per hour offline
• Validator equivocates — material slashing

For CASP staking-as-a-service, slashing falls on the CASP under Article 75(7) unless properly allocated. CASPs that bear slashing risk typically:

• Operate validators in-house with rigorous redundancy and monitoring
• Limit validator concentration to reduce double-sign exposure
• Maintain operational-risk capital buffers beyond Article 67 minimum
• Document the loss-compensation framework in client service terms

CASPs attempting to allocate slashing risk to clients via service terms face Article 7 fair-clear-not-misleading scrutiny — the disclosure must be specific, prominent, and demonstrably understood by the client.

Lock-up disclosure as substantive obligation

Many staking protocols involve lock-up periods during which staked assets cannot be unstaked or transferred. Ethereum’s unstaking queue, Solana’s epoch unstaking, Polkadot’s 28-day unbonding — all examples.

For CASP staking-as-a-service, lock-up disclosure is part of Article 7 substantive obligation:

• Duration of lock-up
• Conditions for early exit (if any)
• Fees or yield-loss for early exit
• Variable lock-up periods (queue-dependent)

Marketing that emphasises staking rewards without proportionate lock-up disclosure breaches Article 7. Some CASPs in early 2026 received supervisory engagement on this specific pattern.

The buyer’s view

For a CASP scoping a staking-as-a-service launch in 2026:

1. Classify the service first. Pure custody plus delegation, or custody plus integrated staking infrastructure, or liquid-staking issuance — the classification drives the regulatory regime.

2. Build the slashing-risk operational framework before launch. Validator redundancy, monitoring, capital buffer. The Article 75 loss-compensation exposure is real.

3. Disclosure is substantive. Risk warnings, lock-up periods, validator selection, reward variability — all required pre-contractual disclosure. Marketing that minimises these compromises Article 7 compliance.

4. Plan for ESMA 2026 review impact. The MiCA Article 142 Commission review will likely produce sharper staking guidance. Operating models should anticipate tighter classification rather than rely on current ambiguity.

For users assessing staking services from a CASP:

• Confirm the CASP is MiCA-authorised for custody and the staking service set
• Read the slashing-risk allocation in service terms
• Understand the lock-up period and early-exit conditions
• Check the validator-selection methodology and concentration
• Verify the reward calculation and distribution mechanism

Staking is one of the more operationally complex services CASPs offer under MiCA. The substantive compliance lift is real but tractable. The classification questions — particularly for liquid staking — will sharpen in late 2026 and 2027 as ESMA convergence work produces clearer guidance.