← current version of this provision

MiCA Recital (59) — 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.

(59) Asset-referenced tokens and e-money tokens should be deemed significant when they meet, or are likely to meet, certain criteria, including a large customer base, a high market capitalisation, or a large number of transactions. As such, they could be used by a large number of holders and their use could raise specific challenges in terms of financial stability, monetary policy transmission or monetary sovereignty. Those significant asset-referenced tokens and e-money tokens should, therefore, be subject to more stringent requirements than asset-referenced tokens or e-money tokens that are not deemed significant. In particular, issuers of significant asset-referenced tokens should be subject to higher capital requirements, to interoperability requirements and they should establish a liquidity management policy. The appropriateness of the thresholds to classify an asset-referenced token or e-money token as significant should be reviewed by the Commission as part of its review of the application of this Regulation. That review should, where appropriate, be accompanied by a legislative proposal.
CELEX: 32023R1114 · provision: 59
Locator: Recital (59); PDF page 8; derived-text line 518
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_59/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': 6

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.