On-chain and off-chain recordal: what the decision maker looks at
When a tokenised right needs to move from one holder to another, the decision maker checks three things first: does the on-chain transfer match the off-chain instruction, has the underlying register accepted the change as final, and has a cut-off date already passed. A file that fails any one of these three checks does not move forward, no matter how complete the ledger transaction itself looks.
This procedure sits inside a wider set of files on tokenised rights and digital objects that track register practice across several jurisdictions — see Coverage map: 40 jurisdictions, 13 register families in practice for the current scope. What follows sets out the stages, the documents a decision maker expects to see, and the point past which a filing can no longer be withdrawn.
Why the two records rarely align on the first try
A tokenised right normally exists in two places at once: as an entry on a distributed ledger and as a line in a conventional register — a land file, a share ledger, a licence file, depending on what the token represents. The two entries are meant to describe the same fact. In practice they drift apart for ordinary reasons.
The wallet address on the ledger side rarely carries a name. The off-chain register, by contrast, is built around named holders. Reconciling the two means someone has to show, in writing, that a specific wallet belongs to a specific named party at a specific moment. Timing gaps matter too: a ledger settles in minutes, while a register update can sit in a queue for days. The decision maker is the person who has to decide, given that gap, which record is authoritative right now.
What to prepare before filing
Preparation happens off-chain first. The ledger entry is evidence; it is not, on its own, the thing a register accepts.
- Assemble the off-chain instrument — the deed, transfer form, or assignment — before touching the ledger record. This is what the decision maker reads first.
- Extract the transaction hash, both wallet addresses, and the settlement timestamp from the ledger side.
- File both records together, in one submission, to the register operator or forum handling the request.
- Ask for a written receipt with a case or ticket reference — do not rely on an automated confirmation alone.
- Note any cut-off date the register imposes for settlement finality, and calendar it separately from the filing date.
- If the request is refused, escalate through the decision maker's own appeals channel within the window it states, not on your own timetable.
| Stage | What the decision maker checks | Who acts | What typically delays it |
|---|---|---|---|
| Intake | Off-chain instrument matches the on-chain hash | Register operator's intake team | Mismatched wallet or missing timestamp |
| Verification | Holder identity and signed consent | Compliance officer | Missing or unclear signature |
| Recordal decision | Whether to update both records as one fact | Decision maker (operator or forum) | A competing priority claim on the same right |
| Confirmation | Written notice sent to both sides | Register operator | Notice period not yet expired |
Who decides, and where
In the first instance, the decision maker is whoever operates the off-chain register: a compliance team inside the register operator, or a designated recordal officer where the register is run by a public body. This first-instance decision is administrative, not judicial, and it usually comes with a stated response window of its own.
If either side disputes the outcome, the matter escalates to the register's own appeals panel where one exists, or to the forum with jurisdiction over the underlying asset where it does not. Recordal disputes rarely go straight to a court; the register's internal process is meant to absorb most of them first.
Common branches
If the off-chain register has no published rule for tokenised transfers at all, the decision maker treats the ledger entry as supporting evidence only, not as the transfer itself. The off-chain instrument still has to carry the weight of the change on its own.
If the underlying token's own listing was refused before the transfer was even filed, the recordal request cannot proceed on a separate track. Resolve that first — see A listing is refused token issuance the deadline that matters before refiling the recordal request.
If a third party claims priority over the same right while the recordal is pending, the decision maker typically suspends the file rather than choosing between the two claims itself. Suspension is not a refusal; it is a hold pending a separate priority finding.
Sources and limits
This page does not establish whether a competitor's claim already has priority over yours. That is a factual check on a specific register, not a procedural question, and it needs a targeted look rather than a general description. Our asset report answers it directly: Asset report when a competitor claims priority sets out exactly what such a check can establish.
Nor does this page cover checks on an off-chain holder's standing where the underlying obligation sits in a national register rather than on a ledger. Where the holder is based in Estonia, Debtor in Estonia shows what that register confirms and what it leaves open.
Related reading
A related file covers enforcement rather than recordal. Where a claim is brought against a token holder directly, the checks differ in one key respect — priority of the claim, not accuracy of the record: How enforcement against a holder tokenised rights what the decision maker looks at in that separate procedure.
If the register in your case sits inside an outsourced custody arrangement and a supervisor has already raised questions about that arrangement, that is its own procedural track: When outsourcing is challenged by the supervisor in practice sets out what to do first.
Reviewed
Reviewed: current at the time of publication. This page describes decision-maker practice as observed across register operators and their published intake procedures; it does not cite specific statutory provisions, since none of the register practices described here has a settled national implementing text confirmed across our coverage.
Frequently asked questions
How long does on-chain and off-chain recordal take in practice?
There is no single figure. Timing is set by each register operator's own procedure and by how quickly the off-chain instrument and the ledger record can be matched. A clean file with no dispute moves faster than one where identity or a competing claim needs checking first.
Which documents are needed to start?
At minimum: the signed off-chain instrument transferring the right, the ledger transaction hash and both wallet addresses, and proof of the holder's identity on the receiving side. Some registers also ask for a statement confirming no competing claim is known at the time of filing.
What happens if the other side does not respond?
Most register procedures set a notice period before they act unilaterally. If that period runs without a response, the decision maker may proceed to record the change on the basis of the filing party's evidence alone, or reject it for lack of confirmation — the outcome depends on the specific register's own rule, not on a general default.