When a right is pledged on-chain: what to do first
A tokenised right can be pledged the same way as its paper equivalent, but the record of that pledge now sits on a distributed ledger. The first task is not enforcement. It is establishing, within hours, whether the pledge is valid, when it took effect, and who currently controls the wallet or account where the token sits.
Legal basis
Regulation (EU) 2023/1114 (MiCA) sets duties for a crypto-asset service provider that holds or transfers the pledged token on a client's behalf. These include safekeeping and record-keeping duties that matter once a pledge is asserted.
Regulation (EU) 2023/1113 (TFR) requires that transfers of crypto-assets carry originator and beneficiary information. That becomes relevant the moment a pledgee tries to trace where a token moved after the pledge was registered.
The pledge itself — its creation, priority and enforcement — is governed by the national law applicable to the underlying right, not by either regulation. Neither act creates the pledge; both shape what a service provider must record and disclose once one exists.
What changes in practice
Once a pledge is asserted, three things change. The token typically becomes non-transferable at the technical layer, either through a smart-contract lock or a hold instruction at the custodian. The priority of the pledge is fixed from the moment of valid registration, not from the moment someone raises a dispute. Any onward transfer that ignores the lock creates a paper trail under the transfer-information duties in TFR, which later becomes evidence rather than protection.
This is why the sequence of first actions matters more than the eventual argument in court. A pledgee who waits to build the full legal case, instead of securing the record first, often finds the record has already moved.
What to do first
- The pledgee confirms the wallet address, contract identifier, and the exact clause under which the pledge was created, before contacting anyone else.
- The pledgee or its counsel checks whether the custodian or issuer has already frozen the token, or whether a freeze request still needs to be sent.
- The custodian, if one is involved, is asked in writing to confirm its MiCA safekeeping status and whether it holds the private key or only an intermediary record.
- Counsel maps which national law governs the underlying right, since that law, not the token's technical layer, decides validity and ranking.
- The pledgee preserves a timestamped copy of the on-chain state before any further transaction can alter it.
- The pledgor is notified formally, in the form the governing law requires, so that the clock on any statutory response period starts running from a fixed date.
Who decides
Two forums usually compete for the same dispute. One is a civil court applying the governing national law. The other, where a licensed intermediary is involved, is that intermediary's internal dispute process under its MiCA authorisation. Neither substitutes for the other; the court decides validity and priority, the intermediary decides only whether it acted correctly on the instructions it received.
| Situation | Who decides | Typical first move |
|---|---|---|
| Pledge recorded via a licensed custodian | Civil court, with the custodian as a fact witness | Written freeze request to the custodian |
| Peer-to-peer pledge, no intermediary | Civil court only | Formal notice to the pledgor |
| Pledgor disputes the pledge exists | Civil court, on the evidence each side produces | Preserve the on-chain record before it can be altered |
Two scenarios
If the pledged right originated in a public offering of tokens, check whether the underlying white paper is still current; a lapsed or unupdated disclosure can affect how a court reads the pledgor's original representations. See When a white paper needs an update in practice for the issuer-side timing that runs in parallel.
If the pledgor has already moved or attempted to move the token after the pledge was asserted, the situation shifts from securing a right to enforcing one, and the applicable steps differ from the ones above.
What this page does not settle
This page does not run a search across on-chain and off-chain registries to confirm what else the pledgor owns or owes; that is a product task, covered by the Asset report czechia.
Where the pledgor is a natural person and the question is exposure rather than the asset itself, the parallel product is the Debtor report czechia.
For a broader view of what each depth of search actually answers, see Three tiers, and the question each of them answers.
Related reading
See the related page, When enforcement is sought against a holder: what to do first, for the creditor-side steps once a pledge moves into enforcement.
Verified
Reviewed 30 December 2024, once both regulations entered into force. Sources: Regulation (EU) 2023/1114 (MiCA); Regulation (EU) 2023/1113 (TFR).
FAQ
What is the first step when a right is pledged on-chain?
Confirm the wallet, contract identifier, and the exact clause creating the pledge before any other action.
Which deadline is already running?
The clock on any statutory response period starts from the date formal notice reaches the pledgor, under the governing national law — not from the date the token was locked.
Who decides, and on what evidence?
A civil court applying the governing national law decides validity and priority, on the on-chain record and the underlying agreement. An intermediary's internal process, where one exists, decides only whether it followed instructions correctly.