New editorial guide, published 16 October 2026. The historical sources linked below are preserved separately and are not represented as current product or service information.
The Blockchains Manager archive contains an April 2023 report about the European Union's Markets in Crypto-Assets Regulation, commonly called MiCA. Its language reflects a moment when a legislative development was being explained before the later application dates. Reading that report today requires more than noticing that the page has an old date. A reader must separate what the source said, which event it described and which primary record answers the present question. This guide develops a research method for doing that. It does not treat the archived article as current law or determine the present authorisation status of any named business.
Give every date a specific event
A proposal, a legislative vote, formal adoption, official publication, entry into force and application are different events. News coverage can compress them into a phrase such as rules approved, but that phrase does not say which obligations apply to whom on that day. Begin by attaching a verb to every date in the report. If the article does not identify the event precisely, record the uncertainty rather than fill it with a familiar interpretation. A chronological table is useful only when its entries describe comparable, clearly identified milestones.
A hypothetical headline might say that a framework has passed while a later paragraph discusses obligations taking effect the following year. These statements need not contradict each other. They may describe different stages. The research task is to locate the primary record for each stage and preserve the distinction in the summary. A reader asking what happened politically on one date is asking a different question from a business asking which provision applied to a particular activity on that same date. The answer must match the question's event and scope.
Use the application provision, not an approximate countdown
MiCA provides a concrete example. Article 149 sets a general application date of 30 December 2024, with Titles III and IV applying from 30 June 2024 and specified provisions applying from 29 June 2023. It separately describes entry into force by reference to publication in the Official Journal. These are distinctions in the primary text, not dates to reconstruct from an old article's approximate countdown. The ESMA rulebook reproduces the provision, making it possible to inspect the actual wording rather than rely on a summary of a summary.
The broader method is to find the provision that governs timing and read its exceptions alongside its headline date. Do not assume that every part of a framework follows one schedule merely because a press release needs a short announcement. Also distinguish the original published text from later consolidated material. A research note should identify the version being used and the question it answers. This creates a traceable basis for the timeline while avoiding a claim that one provision alone resolves every issue about coverage, transition arrangements or a particular entity's obligations.
Keep the framework separate from the entity
A framework existing is not the same proposition as a particular company being authorised for a particular activity. A business announcement can concern an application, a registration, an authorisation, an expansion or a change in operating arrangements. Those words should not be substituted for one another. When the research concerns an entity, identify its legal name and the relevant activity before searching the appropriate official record. A familiar consumer brand may be used by several entities, so a brand-level result may leave the central identification question unresolved.
ESMA maintains an entry point to databases and registers. That is an appropriate starting point for locating relevant official records, not a reason to infer that every entity mentioned in an old news article appears in a particular register. A careful note records the source, observation date and exact scope of what was found. If the available record does not answer the question, the note should preserve that gap. An absence in one search is not automatically proof of every possible status, especially when the search used an incomplete name or the wrong category.
Avoid expanding a narrow finding into a universal conclusion
Suppose a hypothetical company receives approval for one described activity in one arrangement. A headline may shorten that to approved across Europe. The reader should inspect the underlying record before repeating the broader phrase. Which entity received the decision? Which services are covered? Which conditions or limitations are recorded? Does the source describe an issued decision or an intention to seek one? These questions are a way to preserve the finding's boundaries. They do not require inventing a contrary finding or treating every short headline as intentionally misleading.
The same discipline applies to statements about asset categories. A concise explanation may describe an exclusion while omitting the conditions that define it. Repeating the exclusion without those conditions can turn an introductory summary into an inaccurate rule. For the historical MiCA article, the archive preserves the wording as evidence of what the page presented. The new journal does not convert each sentence into present guidance. A current question about an asset's treatment requires the relevant definitions, provisions and facts, rather than a category label lifted from old coverage.
Record the time of your own observation
A regulatory research note has at least two timelines: the events being investigated and the time when the researcher observed the evidence. A page can be updated, a register can change and a previously expected event can be superseded. Record when a source was checked and retain enough identifying detail to find the same record again. An archived screenshot or saved copy can document the observation, but its capture date is still not a substitute for the effective date of the decision or rule it displays.
For a hypothetical ongoing review, keep a short change log rather than overwrite yesterday's finding with today's result. State what changed in the evidence and whether that change affects the previous conclusion. This is especially helpful when a report moves from proposed to adopted, or a company announcement is followed by a formal record. The log makes the research auditable. It also prevents a later reader from mistaking an earlier, appropriately limited statement for a claim that the earlier state continued indefinitely.
Write a conclusion that exposes its evidence
A strong conclusion names the event, its date, the relevant actor and the primary source. It distinguishes confirmed observations from expectations and identifies unresolved scope questions. The wording can remain compact. Instead of a sweeping assertion that regulation has arrived, a note can explain that a specified provision applies from a specified date, while a separate question about a named entity requires a register or decision check. This gives the reader a useful result without hiding the research steps that determine its meaning.
The April 2023 report is valuable precisely as a historical observation, not as a timeless summary. Reading it carefully means keeping its publication context visible and checking later questions against the appropriate primary record. Assign an event to each date, inspect the timing provision, identify the entity and preserve the time of observation. These habits make regulatory coverage more intelligible across changing periods. They also allow an archive to retain an old explanation honestly while a new article teaches readers how to understand what that explanation can and cannot establish.
Technical references
- ESMA: MiCA Article 149, entry into force and application ↗
- ESMA databases and registers ↗
- Regulation (EU) 2023/1114, original legal publication ↗
From the recovered archive
- Everything You Need to Know About The EU’s MiCA Cryptocurrency Rules · captured 25 April 2023