MiCA Annex IV — held text

This page is a held version, frozen at the capture below. It is a source for review. It is not advice, and it does not determine whether this provision applies to you.

ANNEX IV MINIMUM CAPITAL REQUIREMENTS FOR CRYPTO-ASSET SERVICE PROVIDERS Crypto-asset service providers Type of crypto-asset services Minimum capital requirements under Article 67(1), point (a)  Class 1 Crypto-asset service provider authorised for the following crypto-asset services: EUR 50 000 —execution of orders on behalf of clients; —placing of crypto-assets; —providing transfer services for crypto-assets on behalf of clients; —reception and transmission of orders for crypto-assets on behalf of clients; —providing advice on crypto-assets; and/or —providing portfolio management on crypto-assets. Class 2 Crypto-asset service provider authorised for any crypto-asset services under class 1 and: EUR 125 000 —providing custody and administration of crypto-assets on behalf of clients; —exchange of crypto-assets for funds; and/or —exchange of crypto-assets for other crypto-assets. Class 3 Crypto-asset service provider authorised for any crypto-asset services under class 2 and: EUR 150 000 —operation of a trading platform for crypto-assets.

CELEX: 32023R1114 · provision: IV
Locator: Annex IV; PDF page 99; derived-text line 7132
Held artifact: docs_evidence/eu-legislation/eurlex-full-text/20260823T093000Z/32023R1114.pdf
Artifact SHA-256: 32c6d21e712dbb719a9a6b2d39e85133f3059d9e02d8d9ce70d35332bd568b8b
Captured: 20260823T093000Z
Extracted with: pdftotext version 4.00
Official source: EUR-Lex
This version: /celex/32023R1114/ANNEX_IV/20260823-32c6d21e/
Corpus Merkle root: 581628a5b36518981241d2b51f048aa46384f30a74bf648ef542c652028cdeff
Membership proof: 10 hashes — see corpus-proof.json
Modal verbs, counted verbatim (not a legal characterisation): 'shall not': 0 · 'shall': 0 · 'must': 0 · 'may not': 0 · 'may': 0 · 'should': 0

To verify independently: fetch the official source above, extract it with the named tool, and confirm the artifact SHA-256 matches. Then check this provision's leaf against the published Merkle root using the proof in corpus-proof.json.