The European Commission's targeted consultation on the review of MiCA devotes one short section to our category. Section 4.4 of the consultation document is headed Prediction markets and perpetual futures, runs to roughly 190 words including both framing paragraphs, and asks five questions. Three of them, numbered 69 to 71, are about prediction markets. Set those three side by side and the interesting thing is not what they ask. It is which of them carries a clause about technology.
The answer is one of three, and it happens to be the question that decides which European rulebook applies. The clause is not a drafting slip and we are not going to treat it as one. It is a boundary, exactly as drafted, and it has a consequence for every operator with European users who read that section in the summer of 2026 and concluded that the European question was about somebody else.
The clause sits on the classification question and on neither of the other two
Question 69 asks whether prediction markets present opportunities or risks for EU consumer and investors, with a Yes and a No box. By our own count of the consultation text the question itself runs to 16 words and names no technology at all. Question 71 asks what substantive requirements should be considered for service providers that provide prediction market services. Fourteen words, no answer options, and again no technology.
Between them sits Question 70: Should prediction markets, where they are DLT enabled and facilitated through smart contracts be governed by MiFID or MiCA? Nineteen words, two answer boxes marked By MiFID and By MiCA, and the only appearance of distributed ledger technology or smart contracts in any of the three. The framing paragraph above the questions carries the same idea in softer form, describing markets that are increasingly conducted on or are structured through DLT, smart contracts and crypto-assets.
So the European file contains an unbounded question about whether the category is good or bad for retail, an unbounded question about what should be required of operators, and a bounded question about which rulebook governs. The one with the clause is the one with legal consequences attached.
The perpetual futures half of the same section is bounded in both of its questions
The other half of section 4.4 shows what a consistent bound looks like. Question 72 asks whether perpetual futures on crypto-assets should be governed by MiCA or MiFID. Question 73 asks what substantive requirements should apply to perpetual futures on crypto-assets and to the service providers around them. Both questions carry the qualifier, and the qualifier is about the underlying rather than about the plumbing.
Two of two on one half, one of three on ours. We have written before about the other asymmetry in the same section, the one in the answer boxes, where the perpetuals question offers a third option for respondents who think neither framework fits and the prediction markets question does not. The perpetuals half of section 4.4 was drafted by someone who knew which product they meant. Our half was drafted around the technology that brought the product to the Commission's attention.
Read MiCA's own perimeter and the clause has nowhere else to be
None of this is mysterious once you read the regulation under review. Article 3(1), point (5) of Regulation (EU) 2023/1114 defines a crypto-asset as a digital representation of a value or of a right that is able to be transferred and stored electronically using distributed ledger technology or similar technology, as published in the ESMA Interactive Single Rulebook. Article 2(4) then says the regulation does not apply to crypto-assets that qualify as one or more of the following, and point (a) of that list is financial instruments.
Put those two together and MiCA reaches a prediction market contract only if the contract is in token form and only if it is not a financial instrument. A venue running a plain central order book with no token on any ledger is not partly in MiCA. It is outside the instrument entirely. A classification question asked inside a MiCA review therefore cannot be asked about that venue, because MiCA has nothing to say about it. We set out how that ordering works from the other direction, for the venue that does tokenise, in our piece on the third European rulebook.
The clause in Question 70 is the edge of the rulebook, not a judgement about the category. The cost of it lands on the half of the category that cannot answer it.
Every substantive answer to Question 70 pushed the test off the ledger
Three organisations published answers to that question. All three ticked By MiFID, and all three used the free text underneath to say that the ledger is not the right place to start.
The Association for Financial Markets in Europe answered on 30 September 2026 that contracts captured by MiFID II should continue to be subject to MiFID, pointing at Annex I, Section C of the directive rather than at any technology. The same submission adds that some components of prediction markets might fall under existing gambling or consumer protection law and should be enforced accordingly. Its answer to Question 71, measured against the four named regulatory blocks it offers on the perpetuals side, is 22 words long, a gap we examined in the piece on the blank requirements box.
Global Digital Finance was blunter. Its submission of 30 September 2026 says prediction market contracts should be classified according to their legal and economic substance, and then states in one line that a monetary payoff or use of DLT does not by itself determine that classification. Its answer to Question 69 says in the same spirit that product design, duration, venue structure and the operator's economic interest matter more to risk than tokenisation alone.
The Hyperliquid Policy Collective, writing from the side of the market that is built on a ledger, argued the same thing against its own apparent interest. Its response encourages the Commission to begin from the distinction between the contracts rather than the technology on which they are recorded, and asks it to resist treating DLT enabled prediction markets as a single category because the ledger on which a contract is recorded does not determine which of these it is.
Three answers, three ticks for MiFID, and three separate arguments that the clause in the question does not carry the weight the question gives it. Nobody in the published record defended the bound.
The supervisory statement describes the category and never names the technology
While the consultation was open, the European Securities and Markets Authority published the document that actually binds firms today. The public statement of 3 July 2026, reference ESMA35-243228190-8148 and announced in a press release the same day, runs to roughly 858 words by our count. In that text the strings DLT, distributed ledger, smart contract and blockchain appear zero times each. The phrase event contract appears sixteen times. The word crypto appears once, in a footnote.
The test the statement does set is not technological. Only event contracts whose event question relates to an underlying mentioned in Section C(4) to (10) of Annex I of MiFID II classify as financial instruments, and those that do are derivatives caught by the national product intervention measures that replaced ESMA Decision (EU) 2018/795. ESMA adds that the commercial name a firm gives the product is irrelevant for the categorisation under MiFID II and that firms must run a careful legal analysis of the product and its functioning. We walked through what would have to change about a venue for either exemption from that ban to reach it in a separate piece.
Where does the technology appear in ESMA's own account? In footnote 1, and only on the MiCA box: contracts in token form that are not financial instruments may be crypto-assets under MiCA. The qualifier is placed exactly where Article 2(4)(a) puts it, and nowhere else.
The risk monitor repeats the same placement in a single sentence
ESMA said it again, at more length, in the second Trends, Risks and Vulnerabilities Risk Monitor of 2026 (ESMA50-1949966494-4282, published 10 September 2026), which gives prediction markets an in depth section of their own. Depending on their characteristics, the report says, event contracts may qualify as financial instruments under MiFID II, fall within the scope of MiCA where they are based on DLT and do not qualify as financial instruments, or be treated as gambling products under national law.
Three boxes, and the ledger condition attaches to one of them. Everywhere else in that section the technology is a risk factor rather than a perimeter: ESMA writes that manipulation and insider trading risks reach new levels on DLT based platforms with limited identity verification, and that pseudonymous participation hinders detection. That is a statement about how hard supervision is on one kind of venue, not a statement about which venues the category contains. The same report notes that the marketing and sale of event contracts in the EU generally requires an EU authorisation that the largest prediction market platforms did not hold as of its publication.
A national circular carried the test down to firms without mentioning a token
The Malta Financial Services Authority passed ESMA's statement to its own supervised population in a circular dated 3 August 2026. It is a short document, roughly 654 words by our count, addressed to investment firms providing investment services subject to MiFID II. In it the strings DLT, distributed ledger, smart contract, blockchain, token, crypto and MiCA each appear zero times.
What the circular asks firms to do is review their product governance, product classification and distribution arrangements, and to assess the legal classification of event contracts, the appropriateness of the target market, compliance with the national measures and the effectiveness of controls against circumvention. It also records ESMA's point that coupons or rewards paid to holders do not change the binary nature of the underlying contract.
That is the shape of the obligation that is live for an operator with European users. It arrives through the instrument test, it is handed down by a national authority to firms, and it contains no technology clause at all. The classification question in the consultation and the classification duty on the ground are bounded differently, and only one of them has a deadline that has already passed.
One member state framed the product question before Brussels framed the ledger question
There is a counterexample in the European record, and ESMA is the one who recorded it. In the same risk monitor, ESMA writes that Malta is the first EU member state to publicly explore a dedicated regulatory framework for prediction markets, and that in March 2026 the Maltese government described the sector as an area of rapid global momentum offering significant opportunities for innovation subject to an appropriate legislative framework.
Whatever becomes of that, the framing is about a product category and the services around it. No ledger appears in it. A member state looking at this from a standing start described it the way the three consultation respondents did, and the way ESMA's own statement does. The technology bound in Question 70 is not how the people who look at this category describe it. It is how the instrument under review is scoped.
The venue with a plain order book was inside two of the three questions
Here is the practical cost, and it is not hypothetical. An operator reading section 4.4 in July 2026 with no token and no smart contract would find its own description in the framing paragraph, find the clause in Question 70, and reasonably conclude that the European question was about tokenised venues. Two of the three questions were open to it. Question 69 asked whether the category presents opportunities or risks to European consumers and investors, which is a question an unleveraged, fully collateralised venue has a strong answer to. Question 71 asked what should be required of prediction market service providers, had no answer options at all, and was the thinnest part of the whole file. Silence there reads as absence.
That window has shut. Checked on 15 November 2026, the Commission's consultation page shows an opening date of 20 May 2026, a deadline of 30 September 2026 at 23:59 CEST, a status of Closed, and no published responses, no summary report and no feedback statement. The public record of what the category told Brussels is still only what respondents chose to publish themselves. The next fixed point is Article 140(1) of Regulation (EU) 2023/1114, under which the Commission is to report to the European Parliament and the Council by 30 June 2027, accompanied where appropriate by a legislative proposal.
What a venue can still put in writing without a form to fill in
A consultation is a form with a closing date. A classification is a document, and nothing about the closing date removes the duty ESMA described on 3 July 2026. The standard we would hold ourselves to, and the one we think the category needs before someone writes a lower one for it, is a dated and public classification note that an operator keeps current and that answers the questions a supervisor would ask first.
At minimum: what the contract pays and at what moment; what the event question points at, and whether that underlying sits in Section C(4) to (10) of Annex I of MiFID II; who stands on the other side of a filled order and whether the operator ever does; whether positions are fully collateralised and unleveraged, so that loss is limited to the amount paid; how outcomes resolve, from which data source, and who may dispute a resolution; and which member states can reach the venue and on what legal basis. Write it before anyone asks, for the same reason the consultation mattered: the first full description of a product becomes the vocabulary everyone else uses. Our reading of how differently that instrument test runs from one member state to the next is in a companion piece.
The best external version of that note is already written, and it was written by someone else. The Global Digital Finance answer to Question 71 asks for transparent order books and participant driven price discovery, full collateralisation, segregation of client funds, conflicts controls, appropriateness and market abuse safeguards, published resolution rules, independent data sources and a clear dispute procedure, with the line that operators should not take positions against clients except through disclosed regulated market making. An operator who can publish that about itself has answered the unbounded questions whether or not it was ever inside the bounded one. That is what our second and fifth directives ask for, and the commitment is open to any firm willing to sign it.