MiCA and DeFi: The 'Fully Decentralised' Grey Zone

The most repeated sentence in EU DeFi compliance is "MiCA doesn't apply to us, we're decentralised." It is also the most dangerous, because MiCA's decentralisation exclusion is narrow, undefined, and being interpreted by authorities who have signalled scepticism toward the blanket version of that claim. This article sets out what MiCA actually says, what "fully decentralised" plausibly requires, and why the safe posture in 2026 is to assume the exemption is narrow until proven otherwise.

TL;DR

• MiCA does not apply to services provided "in a fully decentralised manner without any intermediary."
• MiCA does not define "fully decentralised"; there is no safe-harbour test as of 2026.
• EBA/ESMA have signalled scepticism toward blanket "we are DeFi" claims.
• Prevailing reading: needs both technical and governance decentralisation — smart-contract-only, no legal-entity counterparty/operator, no value-capturing intermediary.
• A DAO label is not sufficient — substance over form.
• 2026 posture: treat the exemption as narrow and evolving; document the analysis; get counsel.

What MiCA actually says

MiCA expressly states that it does not apply to crypto-asset services provided in a fully decentralised manner without any intermediary. That is the entire textual basis for the "DeFi is exempt" position. Two features of that sentence carry all the weight:

1. "fully decentralised" — MiCA gives no definition.
2. "without any intermediary" — the presence of any intermediary defeats the exclusion.

The exclusion is genuine. It is also narrow on its face ("fully", "any intermediary") and undefined in substance. EU authorities have not issued a settled test, and interpretation is expected to develop through 2026 as MiCA is applied and as the EU considers DeFi-specific work beyond MiCA.

What 'fully decentralised' plausibly requires

Absent a statutory definition, the prevailing reading from authorities and practitioners is that qualifying requires both technical and governance decentralisation:

Common features that undermine a "fully decentralised" claim:

• A company operating the front-end / primary access point
• A foundation or core team directing development and governance
• A fee mechanism routing value to an identifiable entity
• Admin keys, upgrade keys, or privileged roles
• Governance concentration that functions as de facto control

If any of these exist, "without any intermediary" is hard to sustain.

Why "we're a DAO" is not the answer

A frequent fallback: "the protocol is run by a DAO, so there's no intermediary." Authorities look at substance over form. A DAO can still present clear intermediation — a legal wrapper, a core contributor team, a treasury-controlling multisig, a fee switch, concentrated governance. The label "DAO" does not establish "no intermediary"; the facts do. Each protocol needs an honest substance assessment, and the assessment usually finds some intermediary surface that has to be reasoned about, not waved away (see DAO accounting and DAO treasury for how these structures actually look operationally).

The cost of being wrong

The asymmetry is the whole point. If a project wrongly assumes the exemption applies and operates a service that is in fact within MiCA scope, it is providing an unauthorized regulated crypto-asset service in the EU — with the same exposure as any unlicensed CASP, including the criminal and market-access consequences that attach to operating without authorization (see PSAN to CASP migration for the enforcement reality). The downside of over-assuming compliance is small; the downside of over-assuming exemption is existential.

That asymmetry dictates the posture: assume narrow until proven otherwise.

Practical posture for 2026

1. Do not treat the exemption as a default. Start from "MiCA may apply" and work to justify exclusion, not the reverse.
2. Run an honest intermediary inventory: front-end, entity, team, treasury control, fee capture, privileged keys.
3. If any intermediary surface exists, assume MiCA-style obligations may attach to that surface and get counsel on scoping.
4. Document the decentralisation analysis — a contemporaneous, reasoned memo is the artefact that matters if challenged.
5. Track the evolving interpretation through 2026; revisit the analysis as authorities clarify.

Where vendors fit

The decentralisation analysis is a legal determination, not a tooling output. Adjacent infrastructure:

• Cryptio — financial records for any entity surface (foundation, ops company, treasury) that does exist.
• Sumsub — KYC/AML where an intermediary surface triggers obligations.
• TaxBit — downstream tax reporting where activity is in scope.

Tooling supports the entity surfaces; it does not decide the exemption.

How Wag3s helps

Where a protocol does have an entity surface — a foundation, an operating company, a treasury-controlling structure — Wag3s Ledger provides the audit-ready financial records and multi-chain reconciliation that surface needs regardless of how the protocol layer is characterised (see multi-chain reconciliation and foundation treasury accounting). See the Ledger product page.

Further reading

• MiCA Regulation: What It Means for Crypto Businesses
• MiCA Implementation Checklist
• MiCA Crypto-Asset Whitepaper Requirements
• MiCA Market Abuse Rules
• MiCA Timeline 2024-2026
• PSAN to CASP Migration (France)
• DAO Treasury Management

Sources

• Regulation (EU) 2023/1114 (MiCA) — EUR-Lex
• ESMA — Markets in Crypto-Assets Regulation (MiCA)
• EBA — Asset-referenced and e-money tokens (MiCA)