When the referenced work is removed: what to do first
Act within hours, not days: capture proof that the referenced work is gone, notify the token issuer in writing, and preserve every trace of the file before caches and mirrors clear it too. The order in which you act shapes what a court, a marketplace, or an issuer's compliance team will later treat as reliable. How a report is produced, dated and cross-checked and why that sequence matters becomes obvious the moment you start assembling your own evidence file rather than relying on someone else's account of what happened.
Why this differs from an ordinary takedown
A tokenised right is not the work itself. It is a pointer to the work, held together with metadata, a hash, and sometimes a licence description. When the referenced work disappears, the token usually keeps trading. Nothing on-chain stops that.
This gap between the pointer and the pointed-to object is the whole problem. A buyer who checks the token today sees something valid. Nobody checking it sees that the thing it describes is gone unless someone recorded that fact at the moment it happened.
The regulatory frame that applies
Where the token is structured as an asset-referenced token, Regulation (EU) 2023/1114 (MiCA) puts the issuer under an ongoing duty to keep the token's documentation accurate. A referenced work that vanishes from the location named in that documentation is a change to the documentation itself, not a side note the issuer can leave unaddressed.
Regulation (EU) 2023/1113 (TFR) applies in parallel whenever the token itself changes hands while the underlying dispute is still open. It governs the information that has to travel with a transfer of crypto-assets. It says nothing about who is right in a dispute over a removed work, and it does not decide ownership questions.
Neither instrument tells a holder what to do in the first hours after a removal. Both become relevant once the first hours are over and someone has to explain, in writing, why they acted when they did.
What changes the moment the work disappears
Removal does not cancel the token holder's rights on its own. It does start several clocks at once, and the marketplace, the issuer, and any counterparty will each read those clocks differently. Waiting to see whether the work reappears is itself a choice, and in most cases it is the wrong one.
Risk moves in one direction only. The longer the gap between the removal and your first documented reaction, the harder it becomes to show that you acted on current information rather than on something already known to be stale.
There is also a quieter risk. Once a removal is public, other holders and prospective buyers start acting on it too, sometimes before you do. A dated, structured response protects your position against their assumptions as much as against the issuer's.
What to do, in order
- Preserve the evidence first. You, or whoever holds the account: take a timestamped screenshot of the missing page, and hash the last known copy of the file if one still exists anywhere.
- Notify the issuer in writing. The token holder or counsel: send a dated notice describing exactly what disappeared, where it used to be, and when you first noticed it was gone.
- Check the token's own documentation. Compliance or counsel: compare what the whitepaper or the listing terms said about the referenced work against what is missing now, line by line.
- Ask the marketplace for its stated reason. The holder or a representative: request the ground for removal in writing, through a formal channel, not through a chat message that disappears with the thread.
- Freeze any pending transfer. Whoever controls the wallet: hold off on moving or selling the token until the reason for the removal is confirmed one way or the other.
- Assemble a single dated file before relying on any of it. Your legal team: bring the screenshots, the notice, the reply, and the whitepaper extract together, in the order events occurred.
Who decides, and on what basis
| Question | Who decides | Basis or forum |
|---|---|---|
| Whether the removal breaches the issuer's disclosure duty | The issuer's compliance function, then the competent authority under national MiCA implementing measures | Regulation (EU) 2023/1114 (MiCA) |
| Whether the marketplace listing is reinstated | The marketplace's own review body | The platform's terms and its stated appeal procedure |
| Whether a transfer of the token during the dispute was properly documented | The obliged entity that handled the transfer | Regulation (EU) 2023/1113 (TFR) |
| Whether the dispute escalates into a legal claim | A court or arbitral body with jurisdiction over the parties | The contract between the parties, or the applicable procedural rules |
None of these bodies act on your behalf automatically. Each one responds to what is put in front of it, and the file you build in the first hours is what gets put in front of it later.
How the next step depends on why the work disappeared
If a rights-holder had the work pulled, the dispute runs between the rights-holder and whoever hosted the file. The token issuer is usually a witness in that dispute, not a defendant, and treating it as one wastes time.
If the marketplace pulled the listing on its own initiative, whether it comes back, and under what procedure, sits entirely on the platform's own terms. A flat refusal at this stage often runs the same course as When a listing is refused in practice, and the first move there is identical: get the refusal in writing before arguing with it.
If the token keeps trading despite the removal, the priority shifts entirely. The question stops being what happened to the original file and becomes what a current holder can actually rely on when they buy in, and on what basis they were told the reference still stood.
A related situation
A close relative of this problem is a collection disappearing from the marketplace rather than a single referenced file going missing. The sequence differs enough to deserve its own answer: see When a marketplace delists the collection: what to do.
Sources and limits
This page does not establish who currently holds enforceable rights to the removed work, and it does not put a figure on any resulting loss. Those questions need a dedicated check against a registry, not a general sequence of steps.
An Asset in Latvia and its limits sets out what a Latvian registry search can and cannot confirm about an asset's current status, which matters once the removed work turns into a contested asset rather than a broken link on a page.
A Debtor report latvia covers the other side of the same dispute, once a claim over the removed work turns into a practical question of who can actually pay or perform if the dispute is resolved in your favour.
Verified
Verified as at 4 June 2025. Primary sources referenced on this page: Regulation (EU) 2023/1114 (MiCA); Regulation (EU) 2023/1113 (TFR).
Frequently asked questions
What is the first step when the referenced work is removed?
Capture evidence of the removal before doing anything else: a timestamped screenshot and, where one still exists, a hash of the last known file. Notify the issuer only once that evidence is secured, not before.
Which deadline is already running?
No single fixed number of days applies here. The relevant clock depends on which document trips first — the token's whitepaper, the marketplace's terms, or a rights-holder's notice — and each one starts counting from a different date. Treat the earliest plausible date as binding until you can rule the others out with evidence.
Who decides, and on what evidence?
Different bodies decide different pieces of this. The issuer's compliance function rules on disclosure, the marketplace rules on reinstatement, and a court or arbitral body rules if the dispute escalates that far. Every one of them works from the dated evidence file you build in the first hours, not from the original file, which by then no longer exists.