Enforcement against a holder: what the decision maker looks at
When a counterparty holds a tokenised right and refuses to comply, the decision maker checks four things: proof of entitlement, the record of custody on the ledger, whether notice was properly given, and whether the holder had a real chance to respond. The technology behind the token is secondary. What matters is whether the paper trail and the on-chain trail tell the same story.
What starts the enforcement track
Enforcement against a holder begins the moment a claimant shows a breach that the holder has not cured within the agreed or reasonable period. Typical triggers are a refusal to transfer a tokenised entitlement back to its rightful owner, a disputed exercise of a right embedded in the token, or a failure to honour terms attached to the token at issuance. The decision maker does not look at the code of the smart contract in isolation. It looks at what the parties actually agreed, and at whether the on-chain behaviour matches that agreement.
Disputes of this kind often trace back to how the token was first offered to the market. Where the underlying question is whether a promotional statement crossed the line into a binding offer, that is a separate and earlier question — see Marketing is treated as an offer token issuance the. Enforcement against a holder assumes that the underlying right already exists and is not itself in dispute.
What changes once the file is opened
Once a claim is opened, three things change for the holder. First, informal negotiation stops being the only track: the claimant now has a documented starting point that a decision maker can rely on later. Second, the clock most parties assumed they had informally is replaced by a formal one, and missed steps inside it carry consequences that informal delay did not. Third, the holder's silence stops being neutral. A decision maker treats a documented, unanswered notice as evidence, not as an open question.
This is the point of no return most holders underestimate. Before formal notice, a dispute can often be resolved by adjusting terms. After it, the record is fixed, and the decision maker works from what was sent and what was not answered.
Step by step: what to prepare
| Step | What is done | Who does it |
|---|---|---|
| 1 | Assemble proof of entitlement: issuance terms, transfer history, wallet or register extracts | Claimant, with counsel |
| 2 | Send formal notice to the holder, stating the breach and the cure period | Claimant's counsel |
| 3 | Record the holder's response, or the absence of one, with a timestamp | Claimant's counsel |
| 4 | Prepare the file for the decision maker: chronology, evidence, requested remedy | Counsel |
| 5 | File the claim with the competent forum and serve the holder | Counsel |
| 6 | Respond to any procedural objection on jurisdiction or standing | Counsel |
Skipping the notice step is the most common error. A decision maker who sees no notice, or a notice with no proof of delivery, treats the claim as premature and sends the parties back a step.
Who decides and how long it takes
The forum depends on what the parties agreed at issuance: a court, or an arbitral tribunal if the terms include an arbitration clause. Either forum looks at the same three questions — is the right established, was notice given, did the holder have a chance to respond — regardless of the ledger technology involved. Timing runs in two stages. The notice-and-cure period is set by the terms or by a reasonable-period standard where the terms are silent. The forum's own timeline then runs from filing to decision, and depends heavily on whether the holder contests the claim or lets it go undefended.
Common branches
If the holder is an entity registered in Estonia and the dispute may end in insolvency-adjacent recovery, the debtor-side picture matters before you file — see Debtor in Estonia.
If the underlying asset behind the tokenised right is itself in question — for example, whether it is still being maintained as represented — that is checked separately, before enforcement, not during it: see Asset report when maintenance is in doubt.
If enforcement is likely to cross into Latvia, because the holder or the assets are there, what can be established there in practice differs from what a claimant assumes — see Jurisdiction in Latvia in practice.
If you are unsure whether your file is even ready for the notice stage, a quick check before committing to the full process is usually the cheaper first move — see Free check overview in practice.
What this page does not cover
This page covers the enforcement stage against a holder who already has an established tokenised right. It does not cover how that right was created, whether it was validly issued, or whether supervisory authorisation for the issuer is in question — those are earlier or parallel questions with their own procedure.
Verified
Reviewed for currency on the date of publication. This page describes procedural steps only. No statute, regulation or case reference is cited here, in line with the scope of this material; readers requiring the underlying legal basis for a specific dispute should raise that separately with counsel.
Related reading
A closely related decision-maker test applies to platform-level disputes over a listed token — see How take-down and delisting procedure tokenised rights what the.
FAQ
How long does enforcement against a holder take in practice?
It depends on the length of the notice-and-cure period in the terms, and on whether the holder contests the claim once filed. An undefended claim moves faster than a contested one.
Which documents are needed to start?
Proof of the entitlement, the issuance terms, a transfer or custody history, and proof that formal notice was sent and, where relevant, went unanswered.
What happens if the other side does not respond?
The decision maker treats documented, unanswered notice as evidence supporting the claim. It does not, on its own, decide the outcome, but it removes the holder's ability to argue that no warning was given.
If your situation involves a related dispute — a challenged outsourcing arrangement or a questioned offering document — the first move is usually the same: get the file in order before you act. See What to do first in this situation or The offering document is questioned token issuance.