Enforcement against a holder: documents to prepare
Enforcement against a holder of tokenised rights starts with a documented record: proof of the underlying right, proof of the holder's current control over the token, and a clear description of the breach. Without these three elements no forum will accept the case. The sequence below sets out what a claimant assembles before contacting the relevant forum, and where Ordering a report overview fits as a preparatory step.
Why the paperwork decides the outcome
Tokenised rights sit on a ledger, but the right itself is defined off-chain, in a contract, a register entry, or a corporate resolution. A forum examining enforcement will ask two separate questions: does the claimant hold a right that can be enforced, and does the respondent hold the token against which enforcement is sought. Each question needs its own paper trail. Confusing the two is the most common reason a filing is returned for correction.
This is also the point where a claim against an issuer diverges from a claim against a holder. The issuance side involves marketing statements and disclosure documents; How marketing review token issuance runs in practice deals with that side. A holder claim is different: it is about custody, transfer records, and the chain of title, not about how the token was marketed.
Documents by category
| Category | What it must show | Typical form |
|---|---|---|
| Right of claim | The origin and scope of the underlying right | Contract, register extract, corporate decision |
| Holder identification | Who currently controls the token | Wallet address, exchange account record, custodian confirmation |
| Breach evidence | What the holder did or failed to do | Correspondence, transaction history, timestamped screenshots |
| Valuation | The measurable loss or exposure | Internal calculation, third-party valuation note |
| Standing | The claimant's authority to bring the claim | Power of attorney, board resolution, assignment deed |
A file missing any one category is usually still accepted, but the forum will pause the case and request the missing piece. That pause consumes weeks, not days, because most forums issue a written deficiency notice rather than a phone call.
What to do
- The claimant collects the underlying right documentation first — a contract or register extract is the anchor for everything that follows.
- An internal or external analyst maps the token's transaction history to the current holder, using ledger data and, where relevant, exchange records.
- The claimant's counsel drafts a short factual statement setting out the breach in chronological order, without legal argument at this stage.
- A valuation figure is prepared and cross-checked against internal accounting, so the claim does not rest on a single unverifiable estimate.
- Standing documents are gathered — power of attorney, resolution, or assignment — so the filing is not rejected on a procedural technicality.
- The complete file is reviewed once as a set, checking that identification, evidence and valuation refer to the same holder and the same event.
Who decides
The forum depends on where the parties are based and where the claim was structured to sit — a civil court, an arbitration panel, or, in narrow cases, a regulator with enforcement powers over the holder's conduct. The forum reviews the file for completeness before it looks at the substance of the claim. A complete file at filing typically moves to a first procedural hearing within a matter of weeks; an incomplete file adds a correction cycle of similar length.
Two or three scenarios
If the holder is identifiable and cooperative, the file above is usually enough to reach a settlement before a forum is even seized. If the holder is anonymous or the wallet sits behind an exchange, identification becomes the first and hardest step, and the claimant may need a separate disclosure request before the substantive file can be completed. If the underlying right itself is disputed — not just the breach — the claimant should expect the forum to bifurcate the case, deciding the existence of the right before it looks at enforcement at all.
The point of no return
Once a formal notice is served on the holder, most procedures treat the claim as commenced: withdrawing it cleanly, without cost consequences, becomes harder from that point. Preparing the full file before service, rather than serving first and completing the file afterwards, is the difference between a controlled process and a reactive one.
Sources and limits
This page describes a procedural sequence, not a jurisdiction-specific legal basis; it does not name a statute or regulation because none is confirmed for this route in our registry. It does not tell you what a report on the counterparty can establish before you file — that boundary is set out in Asset in Finland and its limits.
It also does not cover what a debtor does once a judgment has already been issued against them; that situation, and its own limits, is addressed separately in Debtor report after a judgment and its limits.
Related publications
A related question — what to prepare when the goal is removal from a platform rather than enforcement — is covered in How take-down and delisting procedure tokenised rights documents to.
FAQ
How long does enforcement against a holder take in practice?
A complete file typically reaches a first procedural step within weeks. Each missing document adds a correction cycle of similar length, so preparation time is usually shorter than correction time.
Which documents are needed to start?
Five categories: proof of the underlying right, holder identification, breach evidence, a valuation figure, and standing documents confirming the claimant's authority to act.
What happens if the other side does not respond?
Most procedures allow the claim to proceed on the existing file after a set waiting period, provided service was properly documented. Non-response does not stop the process; it removes the respondent's input from it.
Verified
Reviewed for currency on this publication date. This page describes procedural sequence and practice; it does not cite a specific statute, and no external source is linked for that reason.