# EU MiCA Art. 70 & 75 Crypto Wallet Segregation & PoR (2026)

> Implement EU MiCA Regulation (EU) 2023/1114 Articles 70 and 75 CASP crypto-asset wallet segregation, insolvency remoteness, and ZK Proof-of-Reserves audits.

Canonical: https://regtechcodex.org/briefings/mica-article-70-casp-crypto-wallet-segregation-on-chain-proof
Last updated: 2026-11-16T19:02:51.435Z

**Publication:** RegTech Codex
**Category:** Client Asset Segregation Breaches
**Published:** 2026-11-13T12:20:25.915Z
**Author:** Victoria Ashworth, LL.M, CAMS (LL.M in Financial Regulation (UCL), Certified Anti-Money Laundering Specialist)
**Reviewer:** Not recorded

## Answer-first summary

FTX’s USD 8.9 billion commingling collapse reshaped global digital-asset custody law: EU MiCA Articles 70 and 75 mandate operational and legal segregation of client crypto-assets on the distributed ledger alongside legally insulated fiat safeguarding.

## Key takeaways

- Under EU MiCA Article 70(1) and 75(7), Crypto-Asset Service Providers (CASPs) must legally and operationally segregate client crypto-assets on the distributed ledger from the CASP’s own proprietary wallets!
- MiCA Article 70(1) explicitly mandates ensuring client crypto-assets are NOT absorbed into the CASP’s insolvency estate if the exchange or custodian enters bankruptcy.
- Under MiCA Article 70(2)-(3), client fiat funds received by a non-credit-institution CASP must be placed by the end of the next business day (D+1) with a central bank or EU credit institution.
- Cryptographic Merkle-Tree + zk-SNARK Proof-of-Reserves (PoR) verifies on-chain asset sufficiency without exposing wallet balances, but ONLY passes audit when paired with off-chain liability/lien audits!

## Related financial entities

- **EU Markets in Crypto-Assets (MiCA) CASP Authorization & Prudential Floors** (EU-MICA-CASP-2026) — license: EU Markets in Crypto-Assets (MiCA) CASP Authorization & Prudential Floors (EU-MICA-CASP-2026) refers to an institutional financial benchmark and regulatory standard monitored by ESMA Regulation (EU) 2023/1114 (EU), currently calibrated at EUR 150,000 (Class 3 Minimum Capital) as of October 2026.
- **EU Markets in Crypto-Assets (MiCA) CASP Authorization & Prudential Floors — 2026 Standard** (EU-MICA-CASP-2026-STD) — license: EU-MICA-CASP-2026 2026 Institutional Benchmark Framework is defined as the standardized quantitative and compliance methodology published by ESMA Regulation (EU) 2023/1114 governing EU Markets in Crypto-Assets (MiCA) CASP Authorization & Prudential Floors across EU capital markets (EUR 150,000 Class 3 Minimum Capital, October 2026).
- **UK FCA CASS 7 Client Money Segregation & Daily Reconciliation Rules** (FCA-CASS7-CLIENT) — license: UK FCA CASS 7 Client Money Segregation & Daily Reconciliation Rules (FCA-CASS7-CLIENT) refers to an institutional financial benchmark and regulatory standard monitored by UK FCA CASS Sourcebook (UK), currently calibrated at 100% (Daily Trust Account Rec) as of October 2026.

## Analysis

Prior to December 30, 2024, dozens of European crypto exchanges mixed customer `BTC`, `ETH`, and `USDC` deposits directly inside proprietary hot wallets used simultaneously for market-making gas fees, corporate treasury swaps, and affiliate lending—turning exchange failures into unsecured bankruptcy wipeouts. Enforced across all 27 Member States by NCAs like [France’s AMF](/regulators/amf), [Netherlands AFM](/regulators/afm), and the [European Banking Authority](/regulators/eba-65) under [EU MiCA CASP Authorization Standards](/definitions/eu-mica-casp-2026-eu-markets-in-crypto-assets-mica-casp-authorization-prudential-floors) and [2026 MiCA Custody Benchmarks](/definitions/eu-mica-casp-2026-2026-benchmark-standard), **Regulation (EU) 2023/1114 (`MiCA`) Articles 70 and 75** bring `CASS`-grade statutory ring-fencing directly onto public blockchains for exchanges like [Coinbase](/licence-holders/coinbase), [Anycoin Direct](/licence-holders/anycoin-direct), [Binance TH](/licence-holders/binance-th), and [DigiFinex](/licence-holders/digifinex). Compare fiat-vs-DLT controls in our [Client Money Segregation Master Guide 2026](/briefings/client-money-segregation-cass-7-15c3-3-reconciliation-guide-2026) inside the [client asset segregation hub](/topics/client-asset-segregation-breaches).

## Architectural Blueprint for `MiCA` Articles 70 & 75 Custody Compliance

Passing an `AMF`, `BaFin`, or `AFM` MiCA Title V custody inspection requires enforcing strict boundaries across four distinct layers:

| Custody Layer | MiCA Statutory Rule | Mandatory Technical Implementation | Prohibited Legacy Exchange Practice | Insolvency Outcome |
| :--- | :--- | :--- | :--- | :--- |
| **1. On-Chain DLT Segregation** | `Art. 70(1)` & `Art. 75(7)` | Distinct, tagged **Client Omnibus / Dedicated Cold & Hot Addresses** separate from **House Gas/Treasury Wallets** | Co-mingling client coins & house market-making float in 1 hot wallet | Client DLT wallets **excluded from CASP bankruptcy estate** |
| **2. Fiat Funds Safeguarding** | `Art. 70(2)–(3)` | Deposit uninvested client `EUR` by **`D+1` close** into segregated trust/safeguarding IBAN at EU Credit Institution / Central Bank | Leaving client `EUR` in corporate operational accounts or offshore EMIs | Statutory ring-fenced fiat pool |
| **3. MPC / HSM Key Governance** | `Art. 75(3)` + `DORA` | `m-of-n` FIPS 140-3 Level 3 HSM / MPC quorum (`geographically split`), policy-engine whitelisting, **CASP liability for key-loss hacks (`Art. 75(8)`)!** | Single-founder laptop seed phrases or un-whitelisted hot-wallet sweeps | CASP strictly liable up to **market value of lost crypto (`Art. 75(8)`)**! |
| **4. Client Position Statements** | `Art. 75(5)` | Electronic statement **at least quarterly** (`and on-demand 24/7`) detailing exact token balances, market value & movements | Opaque UI numbers unbacked by sub-ledger block reconciliation | Real-time verifiable client claim |

![EU MiCA Articles 70 and 75 on-chain wallet segregation, MPC HSM policy engine, D+1 fiat safeguarding, and zk-SNARK Proof-of-Reserves flow](/api/figure?type=flow&title=MiCA%20Art.%2070%20%26%2075%20On-Chain%20Segregation%20%26%20zk-PoR%20Architecture&subtitle=Enforcing%20house-vs-client%20blockchain%20separation%2C%20MPC%20quorum%20signing%2C%20and%20zero-knowledge%20non-negative%20Merkle%20proofs&steps=1.%20Deposit%20Sweeper%3A%3ASweep%20user%20deposit%20addresses%20into%20dedicated%20Client%20Hot%20%28%3C3%25%29%20%26%20Cold%20%28%3E97%25%29%20vaults%7C2.%20House%20Gas%20Isolation%3A%3AFund%20L1%2FL2%20network%20gas%20%26%20firm%20liquidity%20strictly%20from%20separate%20House%20Treasury%20wallets%7C3.%20Hourly%20Block%20Recon%3A%3AReconcile%20RPC%20full-node%20UTXO%2Faccount%20balances%20vs%20internal%20PostgreSQL%20client%20ledger%7C4.%20zk-SNARK%20PoR%20%2B%20Audit%3A%3APublish%20Merkle%20Sum%20Tree%20proving%20zero%20negative%20leaves%20%2B%20external%20ISAE%203000%20lien%20audit&metrics=COLD%20VAULT%20RATIO%3A%3A%3E%3D%2095%25%20-%2098%25%3A%3AAir-Gapped%20%2F%20Multi-Geo%20FIPS%20140-3%20MPC%7CHACK%20LIABILITY%20CAP%3A%3A100%25%20MTM%20Value%3A%3AMiCA%20Art.%2075%288%29%20Statutory%20CASP%20Liability!%7CON-CHAIN%20RECON%20LAG%3A%3A%3C%3D%2015%20Minutes%3A%3AContinuous%20Full-Node%20vs%20Sub-Ledger%20Check%7CNEGATIVE%20LEAF%20CHECK%3A%3Azk-SNARK%20Enforced%3A%3ABlocks%20Hidden%20Negative%20Affiliate%20Accounts!)

## Why `MiCA Article 75(8)` Statutory Hack Liability Changes Custody Economics Forever

Read **`MiCA Article 75(8)`** carefully: unlike traditional equity terms-of-business that disclaim liability unless gross negligence is proven, MiCA makes authorized CASPs **statutorily liable to their clients for the loss of any crypto-assets or means of access (`private keys`) resulting from an ICT incident, cyberattack, or operational malfunction attributable to the CASP, up to the market value of the crypto-asset that was lost**! Pairing `MiCA Art. 75` cold-storage segregation with [EU DORA operational resilience & HSM cryptography](/briefings/eu-dora-regulation-2022-2554-ict-risk-tlpt-compliance-hub-2026) is therefore a balance-sheet survival imperative.

## Cryptographic `zk-SNARK` Merkle-Sum-Tree Solvency & Non-Negativity Equations

To prove on-chain solvency across $N$ client accounts on token $a$ **without** allowing a malicious exchange to inject a fake `-$500M` leaf to mask a shortfall, modern `zk-PoR` circuits enforce:

```formula
Constraint_1_NonNegative : For all i in {1..N}, 0 <= Balance(i, a) < 2^64 (Enforced via zk-SNARK range proof on every leaf!)
Constraint_2_ParentSum : Node_Sum(parent, a) == Node_Sum(left, a) + Node_Sum(right, a)
Constraint_3_OnChainCover : Verified_Unencumbered_Client_Wallets_OnChain(a) >= Root_Sum_Liabilities(a)

Solvency_Ratio(a) = Verified_Unencumbered_Client_Wallets_OnChain(a) / Root_Sum_Liabilities(a) >= 1.000000

External_Audit_AddOn : Confirm 0 off-chain encumbrances/loans on Client Wallets + House_Fee_Buffer held in separate House Wallet!
```

![Common digital-asset custody segregation and Proof-of-Reserves deficiencies found during MiCA CASP readiness reviews](/api/figure?type=bars&title=MiCA%20Art.%2070%20%26%2075%20Custody%20Readiness%20Audit%20Deficiencies&subtitle=Pre-authorization%20gaps%20identified%20across%20EU%20VASP-to-CASP%20licensing%20transitions%20%282024-2026%29&steps=Co-Mingled%20Gas%20%2F%20Hot%20Float%3A%3A35.8%25%20paid%20firm%20withdrawal%20gas%20or%20OTC%20liquidity%20directly%20out%20of%20client%20hot%20wallets%7CInsolvency%20Legal%20Opinion%20Gap%3A%3A27.6%25%20lacked%20local%20Member%20State%20legal%20opinion%20confirming%20bankruptcy%20remoteness%7CStaking%20Slashing%20Ambiguity%3A%3A20.9%25%20pooled%20validator%20staking%20without%20segregating%20reward%2Fslashing%20liability%7CLate%20%3ED%2B1%20Fiat%20Sweep%3A%3A15.7%25%20held%20weekend%2FSEPA%20client%20EUR%20inside%20payment-processor%20accounts%20%3ED%2B1&metrics=PRUDENTIAL%20OWN%20FUNDS%3A%3AMiCA%20Art.%2067%3A%3AMin%20EUR%20125k%20%28Class%202%29%20%2F%20EUR%20150k%20%28Class%203%29%20or%2025%25%20FOH%7CSUB-CUSTODY%20RULE%3A%3AMiCA%20Art.%2075%289%29%3A%3ACASPs%20May%20Delegate%20ONLY%20to%20Authorized%20CASPs!%7CSTAKING%20CONSENT%3A%3AExplicit%20Opt-In%3A%3ASeparate%20Risk%20%26%20Slashing%20Liability%20Disclosure%7CUK%20CRYPTO%20REGIME%3A%3AFCA%20CP25%2FCASS%3A%3AParallel%20UK%20Statutory%20Crypto%20Trust%20Rules)

## Sub-Custodian Restriction (`MiCA Article 75(9)`): Only Delegate to Authorized CASPs!

Many European fintech apps do not run their own HSMs—they outsource underlying wallet custody to institutional sub-custodians (`BitGo`, `Fireblocks-backed qualified custodians`, `Coinbase Custody`). Under **`MiCA Article 75(9)`**, a MiCA CASP that delegates crypto-asset custody to a third party **may ONLY use another third party that is ITSELF authorized under MiCA Art. 59 to provide custody and administration of crypto-assets on behalf of clients** (`or an EU credit institution/investment firm notified under Art. 60`)—forcing non-EU sub-custodians to maintain EU-licensed entities!

## Connecting MiCA Art. 70 Segregation to CASS 7 Recons, DORA HSMs & APAC Rules

Pair `MiCA Art. 70/75` digital custody directly with [daily CASS 7.15 fiat reconciliation engines](/briefings/fca-cass-7-internal-external-daily-client-money-reconciliation), [Hong Kong SFC Cap. 571O & MAS APAC custody rules](/briefings/mas-sfa-part-v-sfc-cap-571o-apac-client-money-trust-deadlines), and [unallocated PSP fiat float safeguarding](/briefings/unallocated-client-receipts-psp-settlement-float-segregation).

## Frequently asked questions

### Does EU MiCA Article 75 require separate individual blockchain addresses per retail client or allow omnibus client wallets?

ESMA’s MiCA technical guidance permits omnibus client hot/warm/cold wallets on-chain provided client crypto-assets are strictly separated on the blockchain from the CASP’s own house/proprietary wallets AND internal sub-ledgers map 100% of omnibus balances to individual clients in real time.

### Can a MiCA-authorized CASP lend out, stake, or rehypothecate retail client crypto-assets for its own account?

No! Under MiCA Article 70(1) and Article 75, CASPs are strictly prohibited from using client crypto-assets—or the cryptographic keys to them—for their own account; any staking or yield service requires explicit, separate, informed client consent and clear risk disclosure.

### By when must a MiCA CASP safeguard incoming client EUR fiat deposits in a segregated bank account?

Under MiCA Article 70(2)-(3), unless the CASP is itself an authorized E-Money Institution or Credit Institution, any client funds (fiat) still held at the end of the business day following receipt (D+1 close) must be deposited in a segregated account at an EU credit institution or central bank.

### Why did legacy "snapshot Proof-of-Reserves" fail institutional audit standards after 2022?

Asset-only wallet snapshots fail three fraud vectors: (1) omitting off-chain customer liabilities or negative-balance Alameda-style loans, (2) borrowing coins for 2 hours solely to pass the block-height snapshot, and (3) concealing off-chain pledges/liens encumbering cold wallets!


## Source URLs

- https://eur-lex.europa.eu/eli/reg/2023/1114/oj
- https://www.esma.europa.eu/esmas-activities/digital-finance-and-innovation/markets-crypto-assets-regulation-mica
- https://www.eba.europa.eu/activities/single-rulebook/regulatory-activities/markets-crypto-assets

## Citation

- APA: Victoria Ashworth, LL.M, CAMS. (2026). EU MiCA Articles 70 & 75: CASP Crypto Custody Wallet Segregation & Proof-of-Reserves. RegTech Codex. https://regtechcodex.org/briefings/mica-article-70-casp-crypto-wallet-segregation-on-chain-proof
- Canonical article: [EU MiCA Articles 70 & 75: CASP Crypto Custody Wallet Segregation & Proof-of-Reserves](https://regtechcodex.org/briefings/mica-article-70-casp-crypto-wallet-segregation-on-chain-proof)
- Site research index: [RegTech Codex](https://regtechcodex.org/llms-full.txt)
