When a white paper needs an update: what to do first
A white paper needs an update whenever the facts it describes stop matching reality: a change to the token's rights, to the issuer's identity, to the trading venues, or to the risks disclosed. The first task is not to rewrite the document. It is to work out whether the change is already material enough to trigger a formal notification, and from which date the clock on that notification starts running.
What sets the obligation
Regulation (EU) 2023/1114 (MiCA) treats a white paper as a live document rather than a one-off filing. Where the underlying facts change materially, the issuer is expected to bring the text back in line and to route the update through the same channel used for the original notification. The regulation does not hand out a fixed checklist of "material" changes. It leaves the first assessment to the issuer, and a later check to the competent authority once the update is filed.
This matters for sequencing. An issuer that waits for a checklist to appear before acting is, in effect, deciding on its own that no update is needed yet — and that decision carries the same exposure as a wrong materiality call made on purpose.
What changes in practice
Once a change is treated as material, three things move at the same time. The notification deadline starts running from the date of the change, not from the date someone drafts the update. The previous version of the white paper stops being reliable for new investors reading it after that date. And any marketing material built on the old text becomes exposed, because it now repeats a disclosure that the issuer itself no longer treats as current.
Delay does not pause any of this. It only shortens the time left to react once the gap between the document and the facts is noticed, whether by the issuer, by a counterparty, or by the authority.
| Type of change | Typical trigger | What usually follows |
|---|---|---|
| Rights attached to the token | New feature, changed redemption terms, changed supply mechanics | Revised white paper, re-notification |
| Issuer or offeror identity | New entity added to the chain, change of control | Updated issuer section, fresh internal review |
| Risk factors | New market, new technology dependency, new counterparty | Expanded risk section |
| Trading venues | Listing added or removed | Updated venue disclosure |
What to do first
- Log the change with a date. The person who approves the update must record when the underlying fact changed, not when someone happened to notice it.
- Assess materiality section by section against the current white paper, rather than making a single yes-or-no call for the whole document.
- Freeze any marketing that repeats the outdated version until the assessment is closed.
- Draft the revised sections and route them through the same internal sign-off used for the original filing.
- Notify through the same channel used for the original white paper, and keep proof of the submission date.
- Record the reasoning behind the materiality call, even where the conclusion is that no notification was required.
Who decides
The materiality assessment starts with the issuer's own compliance function, but the national competent authority responsible for crypto-asset supervision keeps the final say once the notification is filed. It reviews the update against the same criteria used for the original document, and it can ask for further changes before treating the file as closed. Nothing in this sequence gives the issuer the last word on its own assessment.
Common forks
If the change concerns only wording or formatting, an update without a fresh notification is usually enough — the authority still expects a written record of why no notification was needed.
If the change affects the token's rights or the disclosed risk profile, the update is treated as material by default. The notification route applies even if the issuer privately disagrees with that classification.
If more than one jurisdiction is involved, because the issuer or a distributor operates elsewhere, the update has to satisfy the strictest of the applicable notification routes, not the most lenient one available in the group.
What this page does not solve
This page does not establish what a specific white paper currently says, who the issuer of record actually is, or what a given trading venue has already disclosed to its own users. Those are factual questions, closed with a dated file rather than with a situational explanation.
A Document in Czechia: what can be established report checks what the current filing actually says, before anyone assumes it needs rewriting.
A Jurisdiction in Czechia and its limits report settles which regime applies once the issuer or a distributor has a presence there.
A Counterparty report czechia confirms who the issuer or distributor actually is, which matters when the trigger for the update is a change in that identity.
Related publications
See also When the issuer changes jurisdiction: what to do first, which covers the closest adjacent trigger for a white paper update.
Verified
Checked as of 6 June 2025 against Regulation (EU) 2023/1114 (MiCA). Our Methodology: collection, cross-checking and dating and who decides page sets out how facts are collected, cross-checked and dated before they are used on this site.
FAQ
What is the first step when a white paper needs an update?
Log the date the underlying fact changed, then assess materiality section by section before drafting anything.
Which deadline is already running?
Once a change is treated as material, the notification deadline runs from the date of the change itself, not from the date the update is drafted or filed.
Who decides, and on what evidence?
The issuer's compliance function makes the first call; the national competent authority reviews the filed update against the same criteria used for the original white paper.