• Pricings

  • Research

    Data Provenance in RWA Tokenization: What to Prove

    November 4, 2026

    5 mins read

    Data provenance shows where tokenized asset data came from and how it changed. What RWA platforms need to prove first, and how to keep the data private.

    TL;DR: Data provenance is the history of a piece of data: where it came from and every change it went through. In RWA tokenization, a token is only as trusted as the data behind it, such as ownership, NAV, collateral and eligibility. zkDatabase keeps that data off-chain and generates a Zero-Knowledge Proof for every update, so counterparties and auditors can check its history without seeing the raw data.
    Data provenance in RWA tokenization: tracing asset data from source to token Every value a token shows on-chain has a history off-chain.
    Data provenance answers three questions about any piece of data: where it came from, who changed it, and how it reached its current state. For a tokenized fund or bond, that data is the asset's identity on-chain: who owns it, what it is worth, whether a holder is eligible and what backs it. When a platform cannot show that history, every party downstream has to take the number on faith or rebuild it from scratch.

    What is data provenance in RWA tokenization?

    In RWA tokenization, data provenance links each on-chain value to its off-chain source and to every step in between. A NAV on a token page should trace back to the fund's inputs, the calculation that produced it and the time it was published. An ownership change should trace back to the register rule that allowed it.
    Tokenization promises one shared record of who owns what. In practice, the World Economic Forum and Accenture found that firms keep "shadow records" next to the token, because it is not always clear which record is legally enforceable (WEF with Accenture, Asset Tokenization in Financial Markets, May 2025). The same report names reconciliation between tokenized systems and internal books as a barrier that can lead to disputes over the official claim on the asset.
    Every shadow record is a provenance problem. Two systems hold two versions of the same fact, and someone has to show which one is right. As tokenized funds move into lending and collateral, that question leaves the back office. A NAV that cannot be traced to its source becomes a risk for every protocol that accepts the token.

    Four kinds of RWA data need provenance

    Most of the weight sits on four kinds of data:
    • Ownership and transfers: who holds the token, and whether each transfer followed the register rules.
    • Valuation: NAV updates, price inputs and the time each value was produced.
    • Collateral and reserves: what backs the token and when it was last checked.
    • Eligibility: the KYC status, investor class and jurisdiction checks behind each holder.
    Regulators are making the first kind concrete. The UK FCA's final rules on fund tokenisation (PS26/7, April 2026) let a fund register run on distributed ledgers, but the person responsible for the register "must retain authority over it", including to correct errors and process court decisions. So every change to the register needs a clear history: who made it, under which rule and when.

    A signature shows the source, not the history

    Most data pipelines today show who sent a value, not how it was produced. A signed price feed or a signed credential names the source. It says nothing about what happened to the data before it was signed. The W3C makes the same point about digital credentials: "Verifiability of a credential does not imply the truth of claims encoded therein" (W3C, Verifiable Credentials Data Model v2.0, May 2025). Our guide to verifiable credentials explains that model.
    Provenance needs the full path: the inputs, each transformation and each query. A public chain could hold that path in the open, but RWA data is private by nature. Investor identities, deal terms and reserve positions cannot go on-chain as raw data.

    How Zero-Knowledge Proofs add provenance without exposing data

    A Zero-Knowledge Proof lets one party show that a statement about data is correct without revealing the data itself. The WEF report names Zero-Knowledge Proofs and fully homomorphic encryption as privacy-enhancing technologies that "protect sensitive data while enabling compliance".
    zkDatabase applies this to the data layer. It keeps sensitive data off-chain and generates a Zero-Knowledge Proof for every insert, update and query, proving that each change was done correctly. The proofs link into one history. A counterparty can check that today's NAV came from the committed inputs through the stated calculation, or that a transfer passed the eligibility rule, without seeing the investor data behind it. Our post on the RWA tokenization audit shows how those proofs connect across issuance, valuation, collateral and transfer.
    A proof covers how the data was stored and processed. It does not show that a real-world input was true: a custodian statement or a valuation report still comes from its issuer, and auditors and fund administrators keep that role. The proof adds evidence anyone can check next to their work, between reports.

    What an RWA platform should prove first

    A practical order, starting with the data most parties depend on:
    1. Register changes: each ownership change followed the register rules, with the time and the rule applied.
    2. NAV and price inputs: each published value came from the committed inputs through the stated method.
    3. Collateral and reserve checks: the backing data was checked against the stated threshold at each update.
    4. Eligibility: each holder passed the required checks, without their identity data going to every venue.
    Start with one data flow that a counterparty already asks about. For most platforms that is NAV or reserves, because lenders and exchanges ask for it before they accept the token. Our overview of how zkDatabase applies to RWA tokenization maps each of these proofs to a data flow.
    Talk to the Team (https://orochi.network/partnership) to map which of your data flows to prove first.