On-chain and off-chain recordal: stages and deadlines
Recordal of a tokenised right rarely happens in one place. The ledger settles the transfer; a separate register — corporate, land, or securities — records the underlying right. The two tracks run on different clocks, and the point where correction stops being possible arrives earlier on-chain than off-chain.
What changes once recordal starts
Once the ledger confirms a transfer, the on-chain record becomes final within the confirmation window set by the network's own consensus rules. The off-chain register still has to catch up. Until it does, the holder shown on the ledger and the holder recognised by the register controlling the underlying right can differ.
During that gap, a competing claim on the underlying asset carries real weight. Some tokens carry rights beyond a transfer of value. A token gives voting rights token issuance who decides is a question that surfaces at exactly this stage, before the off-chain register closes the file.
Stages, in order
The sequence below holds regardless of which asset class the token represents. What varies is who sits behind each step.
- The initiating party prepares an instruction that names both the wallet address and the legal description of the right being moved.
- The custodian or wallet operator broadcasts the on-chain transfer.
- The ledger reaches finality once its own confirmation threshold is met.
- The party responsible for the off-chain side files the change with the register operator, attaching proof of on-chain finality.
- The register operator checks the filing against its own intake rules and updates its record.
- The holder, or counsel acting for the holder, cross-checks both records before relying on either in a dispute.
Who decides, and by when
No single body runs the full sequence. Each stage has its own decision-maker, and its own deadline logic.
| Stage | Who acts | Deadline logic |
|---|---|---|
| On-chain broadcast | Wallet operator or custodian | Immediate, subject to network load |
| On-chain finality | Validator or miner network, by protocol rule | Set by the protocol's own confirmation rule |
| Off-chain filing | Applicant, through the register's counter or portal | Opens once on-chain finality can be shown |
| Off-chain verification | Register operator | Set by the register's own service standard |
| Cross-check | Holder or counsel | Before either record is relied on in a dispute |
None of these deadlines is fixed by a single external clock. Each register publishes its own service standard, and that standard controls how long verification takes.
If your situation differs
If the receiving register is a national company or land registry, filing typically needs a notarised or certified copy of the on-chain confirmation. A screenshot of a block explorer is not accepted on its own.
If the token's protocol embeds an automatic registrar — an oracle that updates the off-chain register through an application interface — stages four and five merge into one. The deadline then compresses to the interface's own service window.
If the counterparty controls the off-chain filing and does not move, the recordal track stalls. At that point the question stops being procedural and becomes one of enforcement.
What this page does not resolve
This page does not resolve a disputed priority claim between two holders.
A competing claim over which party holds priority follows a different arithmetic. See Asset report when a competitor claims priority.
A recordal dispute that surfaces only after a judgment has already been entered follows its own logic as well. See Debtor report after a judgment.
Both of those questions are answered as fixed-scope reports. Three tiers, and the question each of them answers sets out how the scope of each report is defined.
Reviewed: 11 February 2025. Primary sources: the validator network's own confirmation rule and the intake procedure published by the receiving register.
Related reading
A related procedure covers what happens once the holder is identified but does not act. See How enforcement against a holder tokenised rights runs in.
FAQ
How long does on-chain and off-chain recordal take in practice?
The on-chain leg finishes once the network reaches its own confirmation threshold, usually within a fixed and short window. The off-chain leg depends on the receiving register's own service standard, which can run from days to weeks. The two windows do not run together.
Which documents are needed to start?
An instruction naming the wallet address and the legal description of the right, proof of on-chain finality once the transfer settles, and — for most national registers — a notarised or certified copy of that proof rather than a plain export from the ledger.
What happens if the other side does not respond?
The on-chain record does not wait for anyone. The off-chain filing does. If the party controlling the off-chain side does not act, the underlying right stays recorded in the previous holder's name until a separate enforcement step forces the filing.