Metadata verification: stages and deadlines
Metadata verification confirms that the descriptive record attached to a tokenised right matches the underlying asset, its provenance and its current holder. The process runs through a fixed sequence of stages, each with its own working deadline. It ends at a point where the record becomes final and cannot be reopened without a fresh claim.
For background on how such findings are documented and dated, see our overview of How a report is produced, dated and cross-checked overview.
Why the timing matters
Metadata verification is not a formality. A tokenised right is only as reliable as the record attached to it, and that record is checked against source documents before it is treated as settled. Delay at any stage extends the window in which a competing claim can still be filed. Once the confirmation stage closes, the record is locked, and correcting it later requires a new proceeding rather than a simple amendment.
The point of no return falls at the end of the confirmation stage, not at submission. Before that point, an error in metadata can still be corrected on request. After it, the record is treated as final by anyone relying on it downstream.
The verification sequence
The sequence below reflects how a verification file typically moves from intake to confirmation. Each stage has an owner and a working deadline, counted in business days.
| Stage | What happens | Typical duration | Who is responsible |
|---|---|---|---|
| Intake | File and supporting documents are logged and checked for completeness | Same business day | Intake team |
| Field cross-check | Each metadata field is compared against the source document it claims to reflect | One to two business days | Verification analyst |
| Provenance check | The chain of prior holders is traced back to the first recorded issuance | Two to four business days | Verification analyst |
| Conflict window | The file is held open for a competing claim to surface, if one exists | Set at intake, case by case | Review coordinator |
| Confirmation | The record is marked final and closed to further amendment | Same business day once the window lapses | Review coordinator |
The conflict window is the only stage without a fixed length, because it depends on how the underlying right was issued and whether a competing claimant is already known. Every other stage runs to a working deadline that we set at intake and confirm in writing.
Documents needed to start
A verification file cannot open without a minimal document set. In practice, we ask for:
- the original issuance record or minting transaction reference;
- proof of the current holder's identity and control of the relevant wallet or account;
- any prior transfer records held off-chain, such as a bill of sale or assignment;
- a description of the underlying asset that the token is meant to represent;
- contact details for any known prior holder or counterparty.
Missing documents do not stop intake outright, but they do stop the clock. The field cross-check stage does not start until the file is complete.
What to do
- Submit the intake form together with the document set above. Client.
- Confirm receipt and flag any missing item within one business day. Intake team.
- Respond to any follow-up request within the deadline stated in that request. Client.
- Notify the review coordinator immediately if a competing claim becomes known. Client.
- Cross-check every metadata field against the documents provided. Verification analyst.
- Close the conflict window and issue the confirmation notice. Review coordinator.
Who reviews and confirms metadata
Day-to-day checking sits with the verification analyst assigned to the file. Escalation, and the decision to close the conflict window, sit with the review coordinator, who also signs the confirmation notice. Neither role has authority to rule on ownership as such. They confirm that the metadata record matches the documents on file, which is a narrower question.
Where a genuine ownership dispute is raised during the conflict window, the file is suspended rather than confirmed. The dispute itself is then addressed through a separate track, not through the verification process described here.
Common variations
Three situations change how the sequence above plays out.
If the tokenised right is backed by a physical or registered asset, the provenance check takes longer, because off-chain records must be reconciled with on-chain history.
If the token in question funds a development project rather than representing an existing asset, the review follows the issuance side of the process instead. See The token funds development token issuance who decides and.
If a competing claimant appears only after confirmation, the file cannot simply be reopened. A new claim has to be filed and assessed on its own record.
Where the underlying asset has a longer or contested history, the chain of title itself may need reconstruction before metadata can be verified against it. We cover that separately: How chain of title reconstruction on-chain tokenised rights runs.
What this page does not cover
This page describes the metadata check itself, not the resolution of a priority dispute between competing claimants. Where a competitor asserts an earlier claim, the relevant analysis sits in our Asset report when a competitor claims priority.
Nor does it cover what happens once a court has already ruled against a debtor holding the tokenised right. That situation is addressed in our Debtor report after a judgment.
Verification also does not amount to an opinion on title. It confirms that a record is internally consistent and supported by documents. It does not decide who owns the underlying asset if that is genuinely contested.
Verified
Verified on 12 May 2025. This page describes our internal verification procedure as operated at that date. It does not rely on a statutory deadline, because private metadata review of this kind is not governed by a fixed external timetable.
Frequently asked questions
How long does metadata verification take in practice?
Most files move from intake to confirmation within one to two weeks, once documents are complete. The conflict window can extend this if a competing claim is plausible and needs time to surface.
Which documents are needed to start?
At minimum: the issuance or minting record, proof of the current holder's control, any off-chain transfer documents, and a description of the underlying asset. Incomplete files pause the clock rather than being rejected outright.
What happens if the other side does not respond?
If a known counterparty does not respond within the deadline set in the follow-up request, the review coordinator notes the non-response and proceeds on the documents already on file. Silence does not by itself confirm or defeat a claim.