The Trading Platform\
ESMA Q&A 2552 confirms trading platforms need not draft white papers for tokens with no identifiable issuer — but the relief is narrow. It reroutes the burden into Article 76 due diligence, leaves the DAO and hybrid-token grey zones unresolved, and does nothing to lift the 31 December 2027 legacy-token deadline that falls on platforms alone.
Operational analysis of ESMA Q&A 2552 (European Commission response, 18 February 2026) for EU trading platform operators admitting crypto-assets to trading under MiCA. Core finding: platforms are exempt from the Article 5(2) white paper drafting obligation only where a token genuinely has no identifiable issuer (Recital 22 exclusion from Titles II-IV). The phrase "in the cases required by this Regulation" in Article 5(2) means the obligation does not trigger for issuer-less assets like Bitcoin. The relief is real but narrow. The exemption reroutes rather than removes the burden. Q&A 2552 confirms platforms remain bound by Article 76(2) suitability assessments even for issuer-less tokens — covering technical reliability, illicit-activity/on-chain forensics, track record, and anonymisation functions (Monero/Zcash excluded unless tracing tooling exists). To rely on the exemption, a platform must conduct and retain a documented Article 76(2) assessment positively concluding no identifiable issuer exists; a wrong determination attaches Article 15 liability retroactively. Grey zones that remain unresolved: DAOs with concentrated governance and admin-key control (Recital 20 functional "control over creation" test, Minimum Decentralisation Test); hybrid pre-mine plus decentralised-minting tokens; and the undefined "identifiable" threshold (pseudonymous developers, contract addresses, anonymous multisig). NCAs are expected to read the exemption narrowly to stop meme coins escaping Title II by claiming decentralisation. The two-tiered transparency problem (confirmed alongside ESMA Q&A 2654, October 2025): under Article 143(2)(b), trading platforms alone must ensure a compliant, notified white paper exists for every legacy token (admitted before 30 December 2024) by 31 December 2027, or produce it internally or delist. Other CASPs (brokers, OTC desks, advisors) owe only the Article 66(3) hyperlink-and-warn obligation and can intermediate un-notified legacy tokens indefinitely — a structural asymmetry that sits uncomfortably with MiCA's harmonisation objective. The article gives a five-step admission workflow, a 2027 remediation playbook (inventory, segment, engage issuers, build internal production capacity, verify iXBRL formatting under the 23 December 2025 taxonomy, delisting protocol), and six diagnostic questions for compliance officers. Not legal advice. Answers questions like: Do trading platforms have to write white papers for tokens with no issuer? What does ESMA Q&A 2552 say about Article 5(2)? Does the Recital 22 issuer-less exemption remove all MiCA obligations? What is the Article 76(2) suitability assessment? Is a DAO an identifiable issuer under MiCA? How do platforms treat pre-mine plus decentralised minting tokens? What is the 31 December 2027 legacy-token white paper deadline? Why do brokers and OTC desks have lighter white paper obligations than trading platforms? What must a CASP do to admit a token to trading under MiCA?
The Trading Platform's White Paper Trap: What ESMA Q&A 2552 Actually Requires of CASPs Listing Tokens MiCA Edge Cases | Where Innovation Meets Regulation Published: February 2026 On 18 February 2026, the European Commission published its answer to a question that had been generating compliance anxiety across every EU trading venue since MiCA's full application date in December 2024. The question was whether trading platforms that list tokens on their own initiative are required to draft white papers for assets that have no identifiable issuer. The answer in ESMA Q&A 2552 was: no, they are not. That answer resolved one problem and immediately exposed three others. The relief is real but narrow. The Q&A confirms that platforms are exempt from the white paper drafting obligation under Article 5(2) only where the token in question genuinely has no identifiable issuer. For every other token, the obligation stands, the liability stands, and the burden of determining which category applies sits entirely with the platform. Simultaneously, the interaction between Q&A 2552 and the transitional rules under Article 143(2)(b) has formalised what practitioners now call the two tiered transparency problem: trading platforms bear white paper verification and production obligations that brokers, OTC desks, and other CASPs do not, creating a structural asymmetry that sits uncomfortably with MiCA's harmonisation objective. This article maps the full operational consequence of Q&A 2552 for trading platform operators: what the exemption covers, what it does not, the due diligence burden it generates, the 2027 deadline it cannot eliminate, and the grey zones that remain genuinely unresolved. The Architecture of the Problem: Three Articles, One Obligation Chain To understand what Q&A 2552 resolved and what it left open, the obligation chain needs to be read in sequence. Article 5(1) establishes the baseline: no crypto asset can be admitted to trading on an EU platform unless a compliant white paper has been drawn up, notified to the relevant NCA, and published. The white paper must comply with the iXBRL formatting requirements under the final ESMA taxonomy (applicable from 23 December 2025), and the drafting entity carries strict civil liability for misleading, inaccurate, or incomplete information under Article 15. This liability cannot be waived contractually. Article 5(2) is the mechanism that reaches into trading platforms specifically. When admission to trading is sought on the unilateral initiative of the platform operator, rather than the issuer, the platform operator must step into the issuer's shoes and comply with Article 5(1) itself. The platform draws up the white paper. The platform notifies the NCA. The platform assumes Article 15 liability for a document describing a protocol it did not build. Recital 22 provides the carve out at issue in Q&A 2552. Crypto assets that have no identifiable issuer are explicitly excluded from the scope of Titles II, III, and IV of MiCA. Bitcoin is the canonical example. If the Recital 22 exclusion applies, Title II does not reach the asset, which means no white paper is required under the regulation, which means the condition in Article 5(2) ("in the cases required by this Regulation") is not met. The European Commission's answer in Q&A 2552 confirms this reading. The phrase "in the cases required by this Regulation" in Article 5(2) limits the platform's drafting obligation to situations where a white paper is actually mandated. Where Recital 22 exempts the asset, no white paper is required, and Article 5(2) does not trigger. The practical map of what this means for different tokens: | Token Type | Identifiable Issuer? | Title II Applies? | Article 5(2) Platform Burden? | Article 15 Liability Risk? | | | | | | | | Bitcoin | No | No (Recital 22) | No | No | | Ethereum (post Merge) | No (contested) | No (Recital 22, generally) | No | No | | Named project token (team controlled) | Yes | Yes | Yes, if platform initiates listing | Yes | | DAO token (concentrated governance) | Likely yes | Likely yes | Yes, if platform initiates listing | Yes | | Pre mine + decentralised minting (hybrid) | Grey zone | Grey zone | Grey zone | Grey zone | | Legacy token admitted before 30 Dec 2024 | Depends | Deferred until 31 Dec 2027 | Yes, on platform by 2027 | Yes, from 2028 if not remedied | What the Exemption Requires: Due Diligence, Not Freedom from Obligation Q&A 2552 is explicit on one point that practitioners have underweighted. The exemption from Article 5(2) does not relieve a platform from its obligations under Article 76. The Commission confirmed this directly: platforms are not exempt from their general obligations, including the suitability assessment of admitted crypto assets, regardless of whether a white paper exists. This is where the burden shifts rather than disappears. A platform that cannot require a white paper from an issuer because none exists must instead conduct the substantive due diligence that the white paper would otherwise have provided. Article 76(2) requires the assessment to cover four pillars before any token is admitted to trading. Technical reliability. The platform must evaluate the cryptographic integrity of the protocol, the reliability of smart contract code (including audit history and known vulnerability exposure), consensus mechanism resilience, and node distribution. For a decentralised protocol without an issuer to query, this requires independent technical analysis. Illicit activity risk. On chain forensics covering historical interactions with coin mixers, darknet market exposure, sanctions risk, and overall AML/CTF profile. Blockchain analytics tools are the standard instrument. The platform cannot delegate this to the non existent issuer. Track record and reputation. For tokens with identifiable developer communities, this means evaluation of governance history, past protocol failures, and any prior regulatory enforcement. For genuinely issuer less assets, the open source developer community profile is the relevant data point. Anonymisation functions. Tokens with inbuilt transaction obscuring features, Monero and Zcash being the direct examples, must be excluded from admission unless the platform can deploy compliance tooling capable of tracing transaction history for regulatory reporting purposes. There is no issuer to consult on this. The platform must determine it independently. The practical consequence: to rely on Q&A 2552's exemption for an issuer less token, the platform must first conduct a documented Article 76(2) assessment that positively concludes no identifiable issuer exists. That determination, and the supporting analysis, must be retained. If the determination is wrong and an issuer is later identified, the platform has facilitated the unlawful secondary trading of an un notified Title II asset. The liability under Article 15 attaches retroactively. The exemption is not a shortcut. It is a rerouting of the compliance burden from disclosure production toward forensic due diligence. The Issuer Identification Problem: Where the Grey Zones Actually Live The Q&A 2552 framework is clean at the extremes. Bitcoin has no identifiable issuer. A token launched last month by a named development team with a published roadmap and a corporate treasury clearly does. The compliance question is not about the extremes. It is about the significant middle ground. DAOs as issuers. MiCA defines an issuer as a natural or legal person, or other undertaking, who issues crypto assets. Recital 20 clarifies that the test is functional: issuers are entities that have "control over the creation of crypto assets." A DAO that holds an admin key permitting unilateral smart contract modifications, that controls the minting of new tokens, or that can pause secondary trading is exercising control over the asset. The governance structure being labelled