Asset Registry, Oracles and Reconciliation

AI-assisted manuscript. Asset records, values and reconciliation rules below are invented.

Learning objectives

• Distinguish reported data from verification of the referenced asset.
• Trace an external value through source, version and consumer.
• Design discrepancy handling that preserves evidence.

An oracle reports; it does not create the asset

An asset registry identifies records about an asset or interest. An oracle supplies information for a system to consume. Reconciliation compares records that should correspond and investigates differences. These functions can support a tokenization arrangement without proving every assertion about the external world.

The BIS describes the connection between assets, representations and programmable rules. An external fact remains dependent on how that connection is maintained. A signed report can establish which key attested to a value; it cannot, by signature alone, establish that the warehouse is full or liabilities are complete. BIS

For a fund, valuation is also distinct from immediately executable proceeds. Investor.gov explains the portfolio and share layer of funds, including NAV and expenses. A reported NAV needs a valuation date and method; it is not a universal guarantee of immediate cash. SEC: Mutual Funds

Worked example: the stale 100

Imagine a fictional registry reports 10,000 shares outstanding and a valuation of 100 currency units per share as of day 1. A consumer on day 10 displays “verified value: 1,000,000” without showing the date. On day 8 the administrator recorded a liability adjustment lowering assumed NAV to 98, but the oracle update failed.

There are two problems. The consumer uses stale information, and its “verified” label overstates what was checked. The day-1 multiplication was arithmetically correct under that snapshot; it is not the current valuation. A corrected interface should identify the source, date and current unavailable or stale state rather than silently retain an assurance.

Now the token supply reads 10,200 because a new issuance completed while the external register still lists 10,000. Reconciliation should not automatically choose either record as legally authoritative. Preserve the issuance case, payment evidence, register revision and ledger transaction, then apply the authorized correction process. A 200-unit difference is an investigation trigger, not proof of fraud or proof that minting was legitimate.

Source document/version → authorized report → oracle publication
                                              ↓
Consumer checks scope + date + units + currency + revision
                                              ↓
Available / stale / missing / conflicting
                                              ↓
Reconciliation case → authorized resolution → retained history

Define what each check proves

A schema check proves that fields have an expected shape. A signature check proves that a specified key signed specified data. A freshness check compares the report time against a defined policy. An audit or inspection has its own scope, sampling and exclusions. None should be renamed “assets guaranteed.”

Track units and currency explicitly. A value per share and total portfolio assets are different quantities; mixing them can create a large error despite valid JSON. Match the effective date and instrument class when comparing sources. Do not update historical records in place when a correction should preserve earlier decisions.

Test stale, future-dated, wrong-currency, wrong-instrument, missing-signature and conflicting reports alongside a normal update. The consumer that uses the value must enforce the relevant checks. A background monitor reporting an error does not prevent a separate transfer or valuation path from using the bad value.

Common misconceptions

“Onchain means independently verified.” It describes where a statement is recorded.

“A valid signature means the facts are true.” It authenticates an attestation, not the whole external situation.

“Reconciliation means force all records to match.” Differences require evidence and authorized resolution, not arbitrary overwriting.

Risks and limits

This chapter supplies an educational provenance model, not a certified valuation, reserve attestation or asset audit. Source fraud, privileged key compromise, incomplete liabilities and unavailable external records remain possible. The safe response depends on the actual instrument and authorized operational rules.

Exercise and answer

Exercise: A correctly signed report is nine days old and misses an important later liability adjustment. May the consumer call it current verified NAV?

Answer: No. Signature validity does not establish freshness or completeness. Show the report date and stale state, obtain current evidence and follow the defined discrepancy process.

Related learning

Continue in engineering with settlement money and auditability. Apply evidence labeling in Research.

Source map

bis-tokenisation provides international arrangement research; sec-funds provides U.S. fund valuation fundamentals. Retrieval evidence is dated 2026-10-18. The oracle, NAV changes and reconciliation case are original scenarios. No reserve, external register or commercial oracle was directly tested.