When quoting the price of tokenized assets to institutional clients, how should the data source be selected?
The requirements for institutional pricing and proprietary trading data are completely different: if proprietary trading incurs losses, it's their own issue, but if the pricing is wrong, they have to face inquiries from clients. When providing reference prices for tokenized assets to institutional clients, the core standard is not "how comprehensive the data is," but rather "can it be explained"—when clients ask "where does this price come from, and why is it different from elsewhere," they must be able to answer with fields, timestamps, and sources. This article provides a checklist for data source verification in institutional pricing scenarios.
Who is this article suitable for?
- Sales trading desk providing reference prices for tokenized assets to institutional clients;
- Institutional data team responsible for quote data governance;
- Assessing compliance and risk control for quote system data access.
Checklist: Four essential checks before quoting
First check: Scope check. What transaction price are you using for your quote—contract-inclusive or spot-only? Rolling 24H or natural day? Write this scope in one sentence and include it in the data dictionary of the quoting system, so you can read it when clients ask. The methodology for tokenized assets provides a complete explanation of the statistical scope for each field, serving as a reference for writing the data dictionary.
Second check: Timestamp check. Quotes must indicate the Data as of timestamp, and all relevant fields in the system must use the same timestamp. The most common inconsistency scenario: price data taken at 10:00, depth data taken at 10:05; if the market jumps, the two numbers will not match.
Third check: Dual-source check. Key fields (price, depth) must come from at least two data sources, and if the difference exceeds the threshold, manual review is triggered instead of automatic approval. Whether the difference is normal or abnormal depends on the baseline records; without a baseline, there is no basis for judgment. When making baseline records, you can use stock derivatives exchange rankings and stock spot exchange rankings public data as a second reference source, comparing it in parallel with proprietary data sources.
Fourth check: Traceability check. Record the data sources, fields, timestamps, and values used for each quote, keeping them traceable. This serves as a basis for responding to client inquiries and is also a requirement for internal risk control audits.
Selection of reference versions
The same underlying asset may have multiple issuers, product structures, and trading venue versions. Before establishing a reference price, confirm the issuer, product type, trading venue, quoting currency, price type, and data timestamp of the referenced version. Transaction activity and market depth can serve as observational dimensions for selecting reference versions, but cannot replace the institution's own judgment on product structure, availability, and data licensing. For example, QQQ, the details page's "Tokenized Stock Assets" module displays the issuers, chains, and transaction volumes of each version side by side, and the version composition can be combined with tokenized asset section introduction to explain the data sources to clients.
Usage restrictions
- Reference prices are data presentations and do not constitute trading advice; specific compliance requirements for quoting scenarios should be consulted with the legal and compliance departments of the institution;
- Data source capabilities evolve with version iterations, and the checklist should be reviewed annually; common scope issues can be found in tokenized asset FAQ .
Use the four-checklist to verify your quote data sources
Open RootData tokenized asset dashboard , select any underlying asset, and check your existing quote's scope, timestamp, and dual-source baseline—only if all four checks are passed can the quote withstand a client's inquiry.
