← current version of this provision

MiCA Recital (79) — preamble

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.

(79) In order to ensure consumer protection, market integrity and financial stability, crypto-asset service providers should always act honestly, fairly and professionally and in the best interests of their clients. Crypto-asset services should be deemed ‘financial services’ as defined in Directive 2002/65/EC in cases where they meet the criteria of that Directive. Where marketed at distance, the contracts between crypto-asset service providers and consumers should be subject to Directive 2002/65/EC as well, unless expressly stated otherwise in this Regulation. Crypto-asset service providers should provide their clients with information that is complete, fair, clear and not misleading and warn them about the risks associated with crypto-assets. Crypto-asset service providers should make their pricing policies public, should establish complaints-handling procedures and should have a robust policy for the identification, prevention, management and disclosure of conflicts of interest.
CELEX: 32023R1114 · provision: 79
Locator: Recital (79); PDF page 10; derived-text line 651
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/RECITAL_79/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': 7

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.