ESMA Q&A 2552: Crypto-Assets Without an Identifiable Issuer

Skip key takeaways

Key takeaways: ESMA Q&A 2552 and crypto-assets without an identifiable issuer 6

Updated July 21, 2026

Why Bitcoin and Ether need no MiCA white paper, the recital the exemption actually rests on, what platforms still must do before listing an issuerless asset and the civil liability that returns if a determination is later judged wrong.

• On 18 February 2026, nearly nine months after the question was submitted on 28 May 2025, the European Commission answered ESMA Q&A 2552 On 18 February 2026, nearly nine months after the question was submitted on 28 May 2025, the European Commission answered ESMA Q&A 2552: crypto-assets without an identifiable issuer sit outside MiCA Title II, so no white paper is required and Article 5(2) does not apply to platforms listing them.
• The exemption rests on Recital 22, not on any operative article The exemption rests on Recital 22, not on any operative article, and the recital itself excludes Titles II, III and IV while the Q&A answer narrows its own conclusion to Title II only.
• The Article 66(3) hyperlink duty applies only where a white paper is required The Article 66(3) hyperlink duty applies only where a white paper is required, but that condition is the Commission's interpretive reading, not wording that appears in the statute itself.
• The Commission's own answer keeps platforms on the hook regardless The Commission's own answer keeps platforms on the hook regardless: authorization, a suitability assessment and a documented determination that no identifiable issuer exists.
• Neither MiCA nor the Q&A defines when an issuer is genuinely unidentifiable rather than merely hidden Neither MiCA nor the Q&A defines when an issuer is genuinely unidentifiable rather than merely hidden, so the determination is the platform's to make, document and defend.
• If a determination is later judged wrong, national civil liability can snap back If a determination is later judged wrong, national civil liability can snap back: Germany's KMAG Section 19 makes the issuer, offeror, Antragsteller and the trading platform operator jointly liable for rescission, though personal management liability reaches only the issuer's, offeror's or Antragsteller's management bodies.

Copy takeaways

If your platform lists assets with no identifiable issuer, we can walk through what a defensible determination workflow looks like for your architecture.

See our MiCA compliance software development services

Bitcoin has no issuer. No legal entity drew it up, no board notified a national competent authority, no one holds a Legal Entity Identifier on its behalf. MiCA's Title II disclosure machinery, drafting a crypto-asset white paper, notifying it, publishing it, assumes an issuer, an offeror or a person seeking admission to trading exists to do that work. For the first year of MiCA's full application that mismatch sat unresolved on every EU trading platform listing the two largest crypto-assets in the world. On 18 February 2026, nearly nine months after the question was submitted on 28 May 2025, the European Commission closed the gap through ESMA Q&A 2552.

In short: Q&A 2552 confirms that crypto-assets with no identifiable issuer fall outside MiCA Title II, so no white paper is required for them and Article 5(2) does not apply to the platforms that admit them to trading. That answer is the legal ground under every Bitcoin and Ether listing in the EU today. It is also, by its own terms, an administrative interpretation of a recital, not a binding rule. The Q&A's own disclaimer says only the Court of Justice of the EU can authoritatively interpret Union law, and the Commission's answer keeps platforms on the hook for authorization, a suitability assessment and a documented determination that no identifiable issuer exists. We build the listing gates and due-diligence records that turn that determination into an operational workflow rather than a one-time guess.

Why MiCA's Title II architecture assumes an issuer exists

MiCA's Title II obligations, drafting a crypto-asset white paper, notifying it to a national competent authority and publishing it before trading begins, attach to an identifiable issuer, offeror or person seeking admission to trading. The regulation's drafting assumes one of those three roles is always occupied by a legal person who can be named, notified and held to account. Bitcoin does not fit that assumption: its tokens are generated algorithmically by a protocol, and its codebase is maintained by a voluntary and shifting set of developers who do not exercise economic control over issuance in the way a company controls the shares it issues.

Before Q&A 2552, one plausible market reading filled that gap by shifting the whitepaper duty onto the platform: if no issuer exists to draft a document, the CASP seeking to list the asset should draft it instead. That was not a strawman. Law firm client alerts framed MiCA compliance in terms of comply-or-be-delisted, and Benedikt Bartylla, a researcher at Philipps-University Marburg writing on the Oxford Business Law Blog on 4 June 2025, argued that a platform listing an asset on its own initiative "must publish the whitepaper themselves and bear the liability attached (Art. 5(2), 15 MiCAR)". The Liechtenstein exchange LCX states it acted on exactly that reading: it drafted and registered a Bitcoin MiCA white paper through its national competent authority, dated 5 June 2025, carrying the standard disclaimer that the document has not been approved by any competent authority. LCX's own site separately notes the firm "is not currently authorised under MiCA", so the artifact is best read as the clearest concrete evidence of the pre-Q&A over-compliance era rather than as a settled compliance model.

A separate technical impasse compounded the uncertainty. Commission Delegated Regulation (EU) 2025/421 of 16 December 2024 sets the machine-readable format for white papers, Inline XBRL and XHTML, applying from 23 December 2025, and its Article 3 requires an ISO 17442 Legal Entity Identifier for the person drawing up the white paper. For a genuinely decentralized network there is no issuer-side entity to hold that LEI: the format rules assume someone accountable is drawing up the document, which is exactly what an issuerless asset cannot supply. The impasse only dissolves on the reading the Q&A later confirmed, that no white paper, and therefore no LEI holder, is required for such assets in the first place. The question submitted to ESMA on 28 May 2025 asked the Commission to resolve exactly this: does Article 5(2)'s phrase "in the cases required by this Regulation" exempt trading platforms from Article 5 for crypto-assets that have no identifiable issuer at all.

What ESMA Q&A 2552 actually says

The question, verbatim: "Does the expression 'in the cases required by this Regulation' mean that Article 5(2) exempts operators of trading platforms from the requirements of Article 5 for crypto-assets without an identifiable issuer?"

The European Commission's answer, published 18 February 2026 and reproduced here in full because earlier summaries in circulation drop its most consequential passage:

"Yes. Article 5(2) MiCA is not conceptualized to cover cases where crypto-assets have no identifiable issuer and are therefore not subject to Title II of MiCA. The Article requires CASPs operating a trading platform to comply with the requirements set out in Article 5(1) MiCA, where they initiate the admission of crypto-assets to trading and no white paper has been published 'in the cases required by this Regulation'. Hence, this provision is specifically and exclusively limited to cases, where a white paper is required by MiCA. However, as clarified by recital 22, crypto-assets without an identifiable issuer do not fall within the scope of Title II. It follows that no white paper is required for these crypto-assets under MiCA and that, consequently, Article 5(2) MiCA does not apply to them. Nevertheless, in accordance with the wording in recital 22 that CASPs 'providing services in respect of such crypto-assets should be covered by this Regulation', CASPs operating a trading platform are not relieved from obtaining authorisation and complying with their general obligations, including a suitability assessment of any admitted crypto-assets and determination of whether an identifiable issuer exists, i.e. whether a white paper is required. Similarly, and in line with the above, Articles 76(1)(2) and 143(2)(b) MiCA impose requirements on CASPs operating a trading platform and specifically reference to 'cases required by this Regulation'. Finally, Article 66(3) shall be interpreted as meaning that operators of trading platforms must provide clients with hyperlinks to any white papers for the crypto-assets in relation to which they are providing services, provided that a white paper is required under MiCA."

Two things worth naming precisely. First, this is formally an ESMA Q&A database entry, but the answer itself is credited to the European Commission and described on the page as reflecting an internal Commission decision, so calling it "the Commission's ruling" overstates its status and calling it "ESMA's decision" understates who actually wrote it. Second, the passage most summaries skip, beginning "Nevertheless", is where the compliance floor actually sits: the Commission itself, not a law firm's gloss, requires platforms to run a suitability assessment and to determine whether an identifiable issuer exists at all. That duty is primary text, not commentary layered on top of it.

What the answer exempts, and what it leaves standing

Three things follow directly from the text above. No Title II white paper is required for assets with no identifiable issuer. Article 5(2) does not apply to a platform initiating their admission to trading. And the Article 66(3) hyperlink duty, requiring platforms to give clients links to any white paper for an asset they service, only bites "provided that a white paper is required under MiCA". Worth stating plainly: the text of Article 66(3) itself contains no such condition. Its statutory wording reads, in full: "Crypto-asset service providers shall warn clients of the risks associated with transactions in crypto-assets. When operating a trading platform for crypto-assets, exchanging crypto-assets for funds or other crypto-assets, providing advice on crypto-assets or providing portfolio management on crypto-assets, crypto-asset service providers shall provide their clients with hyperlinks to any crypto-asset white papers for the crypto-assets in relation to which they are providing those services." No "where required" qualifier appears anywhere in that sentence. The conditionality is the Commission's own interpretive move in the Q&A answer, read into the article rather than written into it.

The answer also anchors two further provisions to the same "cases required by this Regulation" logic: Article 76(1) and (2), and Article 143(2)(b), a transitional provision most earlier summaries of this Q&A skip entirely. Article 76(1)'s second subparagraph reads: "For the purposes of point (a) of the first subparagraph, the operating rules shall clearly state that a crypto-asset is not to be admitted to trading where no corresponding crypto-asset white paper has been published in the cases required by this Regulation." Article 76(2) adds: "Before admitting a crypto-asset to trading, crypto-asset service providers operating a trading platform for crypto-assets shall ensure that the crypto-asset complies with the operating rules of the trading platform and shall assess the suitability of the crypto-asset concerned." Read together, the missing white paper does not block a listing decision, but the suitability assessment behind that decision, covering technical reliability, links to illicit or fraudulent activity and the track record of the team behind the asset where one is identifiable, still has to happen and still has to be documented.

Recital 22: the whole exemption rests on a recital

Every part of the answer above traces back to a single recital, not to an operative article. Recital 22, in full: "This Regulation should apply to natural and legal persons and certain other undertakings and to the crypto-asset services and activities performed, provided or controlled, directly or indirectly, by them, including when part of such activities or services is performed in a decentralised manner. Where crypto-asset services are provided in a fully decentralised manner without any intermediary, they should not fall within the scope of this Regulation. This Regulation covers the rights and obligations of issuers of crypto-assets, offerors, persons seeking admission to trading of crypto-assets and crypto-asset service providers. Where crypto-assets have no identifiable issuer, they should not fall within the scope of Title II, III or IV of this Regulation. Crypto-asset service providers providing services in respect of such crypto-assets should, however, be covered by this Regulation."

Read that carefully against the Q&A answer and a narrowing appears. The recital itself excludes issuerless assets from Title II, III and IV alike. The Q&A answer, quoting the same recital, confines its own conclusion to Title II only, stating that such assets "are therefore not subject to Title II of MiCA". Nothing in the published answer extends that reasoning to Titles III or IV, which cover asset-referenced and e-money tokens rather than the Bitcoin-shaped case the question was actually asking about. The triangulation is worth sitting with rather than smoothing over: a recital that speaks broadly, a Q&A answer that only confirms the narrower slice of it, and an operative text, MiCA's articles themselves, that contains no corresponding exemption language and no criteria for when an issuer counts as unidentifiable in the first place. That gap in the operative text is exactly why the question was submitted at all.

Whether a recital can carry that much legal weight is itself an open question. Under the doctrine EU courts have applied for decades, most often cited to Case C-162/97 Nilsson, a recital has no binding legal force of its own and cannot be relied on as grounds for derogating from the operative provisions of the act it introduces. Applied here, that doctrine cuts both ways: it is exactly what lets a future court decide the Title II exemption Recital 22 describes does not actually bind anyone, and it is exactly why the Q&A answer that leans on it is, by construction, an interpretation rather than a rule.

Unidentifiable versus merely unidentified

Neither MiCA nor the Q&A answer defines when an issuer counts as unidentifiable. The Commission's own text stops at requiring platforms to make "determination of whether an identifiable issuer exists" without setting out how. Commentators have filled that gap with a distinction the primary text never states: genuinely unidentifiable, an asset like Bitcoin generated algorithmically with no controlling party, against merely unidentified, a project whose founders are simply hiding behind pseudonyms. Crypto Risk Metrics GmbH, a Hamburg firm, put the stakes of blurring that line bluntly: "'having' no identifiable issuer should be a very rare occasion", and a loose reading of the Q&A "could be seen as an invitation for crypto-assets such as meme-coins". Bartylla makes a related point from the other direction, arguing that "not identifiable" should be read to mean fully decentralized rather than merely unknown by name, precisely to keep the exemption from becoming a shelter for projects that are hiding rather than absent.

Ether is the case that shows why the test needs care. Ethereum's 2014 presale was run by identifiable entities and the Ethereum Foundation remains a visible steward of the ecosystem, yet new ETH is generated by the protocol itself and the Foundation neither controls issuance nor stands behind the asset the way an issuer stands behind its securities; the third-party ETH MiCA white papers drafted in the pre-Q&A era name the Foundation as a contributor, not an issuer. On the unidentifiable-versus-unidentified test, and this is our analysis rather than settled law, an asset can have a documented origin story and well-known institutional stewards and still lack an issuer in MiCA's sense, because no present entity issues the tokens or controls whether they are issued. A regulator that weighed the presale history differently could reach another view, which is exactly the exposure a documented determination is built to absorb.

The negative case is just as instructive. An e-money token like Circle's EURC has an issuer no test could miss, an electronic money institution authorized in France since July 2024 that drafts its own white paper and answers for it, while a meme-coin whose founders are merely pseudonymous has an issuer that exists but hides, which makes it unidentified rather than unidentifiable and keeps it inside Title II.

No formal test exists in either the regulation or the Q&A to arbitrate between the two readings, which means divergent national interpretations across competent authorities are the likely outcome rather than an edge case. The consequence, following directly from the Q&A's own logic rather than from speculation, is asymmetric: get the determination wrong, list an asset as issuerless when a national competent authority later identifies a controlling party, and the platform faces the full Title II and Article 5 exposure it believed the Q&A had removed.

Non-binding all the way down

Every layer of this answer is, by its own construction, non-binding. The Q&A page's standing disclaimer states it plainly: "The answers clarify provisions already contained in the applicable legislation. They do not extend in any way the rights and obligations deriving from such legislation... Only the Court of Justice of the European Union is competent to authoritatively interpret Union law." The same disclaimer goes further than most administrative guidance does, noting that even the Commission's own answer cannot prejudge the position the Commission itself might later take before Union or national courts. That is the second layer under the recital doctrine above: an interpretation of a non-binding recital, published with an explicit reservation that the interpreter might argue differently in litigation.

A third layer sits in supervisory practice rather than in the text itself. As compliance commentators note, national competent authorities generally absorb ESMA Q&As into administrative practice unless they publish a contrary position, which is why the Q&A functions as de facto guidance across the EU even though nothing compels a court to follow it.

A fourth layer is where the abstraction becomes a concrete civil liability question, and Germany's implementation offers the clearest example. Section 19 of the Kryptomaerkteaufsichtsgesetz, the German MiCA implementation act, gives a purchaser the right to demand rescission: take-back of the asset against refund of the purchase price and usual costs, or the price difference if the asset was already resold, where a required crypto-asset white paper was not published contrary to Articles 9, 28 or 51(13) MiCAR. The issuer, the offeror, the Antragsteller (the person seeking admission to trading) and the trading platform operator as an entity are joint debtors on that claim. Personal liability of management body members under Section 19(1) reaches only the management of the issuer, the offeror or the Antragsteller, not the trading platform operator's own management as such, though a platform that itself sought the admission to trading for a listing may count as the Antragsteller for that specific listing and see its management reached through that limb.

The chain that follows Q&A 2552 is straightforward until it is not: no white paper required for a genuinely issuerless asset means no publication was ever "required contrary to" the statute, so Section 19 has nothing to bite on. That reading is a reasonable inference from the Q&A, not a statement the Q&A itself makes about German civil liability specifically. If a court or a national competent authority later decides the identifiability determination was wrong, that inference snaps back, and the exposure Section 19 describes returns, potentially including personal liability of the issuer's, offeror's or Antragsteller's management.

The criticism: does this reward anonymity

The Q&A resolves an operational question but leaves an incentive question open. Bartylla's structural argument is the sharpest version of it: MiCA's whitepaper duty was written to fall on an issuer, an offeror or a person seeking admission to trading, plural roles, not on the issuer alone, so an identifiable offeror profiting from a listing is arguably not excused simply because the issuer behind the asset cannot be named. On his reading, a platform that lists an asset on its own initiative should still bear the whitepaper duty and the "uncapped damages under Article 15" that come with getting it wrong, regardless of what Q&A 2552 says about Article 5(2). Crypto Risk Metrics makes essentially the same point from a supervisory angle, warning that a loose reading of the exemption invites exactly the assets MiCA was written to police, and expecting national competent authorities to take a strict rather than a permissive approach to identifiability going forward.

One counter-consideration made the Q&A operationally necessary in the first place, and it belongs beside the criticism above, not instead of it. Forcing a platform to author a white paper for an asset it does not control and cannot bind produces a disclosure document with no accountable issuer standing behind its claims, which is its own investor-protection failure. The LCX artifact described above is exactly that problem in concrete form: a document that satisfies a formality without anyone able to stand behind its content the way an issuer's own white paper implies.

Listing practice since 18 February 2026

What we can verify in the market: the LCX artifact described above still stands. Kraken maintains a public asset-listings white paper hub, surfacing a white paper link per asset in the pattern MiCA-era platforms have converged on. What we could not find, and it is itself informative: as of this article's publication, no national competent authority has published its own position statement on Q&A 2552, and no major CASP has publicly announced a change to its Bitcoin or Ether listing documentation in response to it. The observable market state is that Bitcoin and Ether remain listed EU-wide without MiCA white papers, which is precisely the outcome the Q&A validates rather than a gap in enforcement.

The meme-coin edge is where the Q&A's logic is actually being stress-tested, by assets whose creators are hiding rather than genuinely absent. For now, the strict approach expected of national competent authorities described above is the only real control on that edge case; nothing in the text sets a bright line.

Not every authorized CASP even faces this determination in practice. Only a subset operate trading platforms at all: 20 of 295 active records in the ESMA register, per our own ESMA register data study dated 20 July 2026. The identifiability determination burden concentrates on those 20 firms specifically, the population actually initiating admissions to trading rather than the wider set of CASPs offering custody, exchange or advisory services.

The review will not fix this

The European Commission's MiCA review consultation, open until 30 September 2026, never mentions issuerless crypto-assets at all, so Q&A 2552 remains the only guidance on the books and only a future MiCA v2 package could harden or reverse it; we break down the full consultation in our MiCA Review 2026 guide.

Engineering the determination workflow

When an asset with no white paper comes up for listing on a platform we build, the question is never whether the paperwork can be skipped. It is whether the compliance record that replaces it exists. Our listing gates block an asset from reaching production until the identifiability determination, the suitability assessment and the sign-offs are all recorded. The exemption in Q&A 2552 removes a document, not the decision behind it.

We model the issuer determination as a versioned record, not a checkbox: what evidence was reviewed, genesis mechanics, upgrade keys, treasury control, governance concentration, who assessed it and when it is due for re-review. Neither MiCA nor the Q&A defines "unidentifiable", which means the only defensible position an operator can hold is a documented one.

The Article 66(3) hyperlink duty switches on the moment a white paper exists for an asset a platform lists. We turn the law firms' advice on that point into a scheduled job rather than a manual habit: a watcher that checks the ESMA register for new white papers against a platform's listed issuerless assets and drops any hit into the compliance queue. A duty that can activate overnight should not depend on someone remembering to look.

Q&A 2552 is non-binding, and a national competent authority can probe any listing decision years after it was made. We build listing workflows so every determination is reproducible: the evidence snapshot, the assessor, the rationale and every re-review since. If a regulator asks why an asset traded without a white paper, the answer should be an export, not an archaeology project.

Issuerlessness is not a permanent property, either. A foundation forms, a governance vote concentrates control in one entity, a development company steps out of the shadows, and an asset that was genuinely issuerless at listing may stop being so. We wire re-review triggers to governance events so the determination ages with the asset instead of expiring silently.

How Pharos Production helps

We build the listing and due-diligence infrastructure that sits behind decisions like the one Q&A 2552 governs: identifiability determinations as evidence-backed records, suitability assessments wired into the listing pipeline rather than bolted on afterward, and register watchers that catch the moment a white paper duty switches on. If your platform lists assets with no identifiable issuer, our MiCA compliance software development practice can walk through what a defensible determination workflow looks like for your architecture.

Sources: ESMA Q&A database entry 2552, answer provided by the European Commission (question submitted 28 May 2025, answer published 18 February 2026); Regulation (EU) 2023/1114 (MiCA) Recital 22 and Articles 5, 15, 66, 76 and 143; Commission Delegated Regulation (EU) 2025/421 of 16 December 2024; Benedikt Bartylla, Oxford Business Law Blog (4 June 2025); Crypto Risk Metrics GmbH, Hamburg; LCX Bitcoin MiCA white paper page (lcx.com); Kraken asset-listing white papers hub; Kryptomaerkteaufsichtsgesetz (KMAG) Section 19, official text via gesetze-im-internet.de; our own ESMA CASP register raw-CSV analysis dated 20 July 2026.

FAQ

Last updated: July 21, 2026

Quick answers to common questions about custom software development, pricing, process and technology.

Expand all Collapse all

Search FAQs

Popular

Type to filter questions and answers. Use Topic to narrow the list.

Showing all 7

• ★ Featured question. What is ESMA Q&A 2552?

  Copy link Copies a direct link to this answer to your clipboard.

  An entry in ESMA's Q&A database on MiCA, answered by the European Commission on 18 February 2026, confirming that crypto-assets without an identifiable issuer are outside Title II of MiCA, so no crypto-asset white paper is required for them and Article 5(2) does not apply to platforms listing them.

• ★ Featured question. Does Bitcoin need a white paper under MiCA?

  Copy link Copies a direct link to this answer to your clipboard.

  No. Per Q&A 2552, assets with no identifiable issuer fall outside Title II, so no MiCA white paper is required for Bitcoin; see the listing duties below for what platforms must still do before listing it.

• Is ESMA Q&A 2552 legally binding?

  Copy link Copies a direct link to this answer to your clipboard.

  No. The Q&A's own disclaimer states the answers create no new rights or obligations and only the Court of Justice of the EU can authoritatively interpret Union law. National competent authorities tend to follow ESMA Q&As in supervisory practice, but courts are not bound.

• What must a trading platform still do before listing an asset with no issuer?

  Copy link Copies a direct link to this answer to your clipboard.

  Hold authorization, run the suitability assessment its operating rules require, covering technical reliability, links to illicit or fraudulent activity and the team's track record, and make and document a determination that no identifiable issuer exists, meaning no white paper is required.

• What is the difference between an unidentifiable and an unidentified issuer?

  Copy link Copies a direct link to this answer to your clipboard.

  Commentators draw the line between assets generated algorithmically with no controlling party, like Bitcoin, and projects whose creators simply hide their identity. MiCA and the Q&A give no formal test, so platforms document the assessment themselves and national competent authorities are expected to police it strictly.

• What happens if a platform wrongly treats an asset as issuerless?

  Copy link Copies a direct link to this answer to your clipboard.

  The Title II exposure returns. In Germany, KMAG Section 19 lets purchasers demand rescission from the issuer, the offeror, the Antragsteller (person seeking admission) and the trading platform operator as joint debtors where a required white paper was not published.

  Personal liability of management body members reaches only the issuer's, offeror's or Antragsteller's management, not the platform operator's as such, though a platform that itself sought the admission may count as Antragsteller for that listing.

• Will the MiCA review change the rules for issuerless crypto-assets?

  Copy link Copies a direct link to this answer to your clipboard.

  Not through the current consultation, which never mentions the topic. Q&A 2552 remains the only guidance, and only a future legislative package could codify or reverse it.

I work with startup founders who need a dedicated software development team but don’t want to gamble on hiring, random outsourcing, or opaque delivery.
Most founders face the same problem sooner or later.
Early technical and team decisions lock the product into tech debt, slow delivery, missed milestones and constant re-hiring. By the time this becomes visible, fixing it is already expensive.

As a CTO and software architect, I help founders design, build and run dedicated development teams that work as a true extension of the startup. Not as a black-box vendor.

My focus is on complex products where mistakes are costly:

• Web3 and blockchain platforms
• FinTech and regulated products
• High-load startup systems
• MVP → scale transitions

We don’t do body-shopping.
We don’t sell generic outsourcing.

Instead, we help founders:

• build the right team structure from day one
• keep technical ownership and transparency
• scale delivery without losing control
• avoid vendor lock-in and hidden risks

Teams are aligned with the product roadmap, business goals and long-term architecture. Not just short-term velocity.