A digital-asset catalogue should describe the asset, network context and traded instrument independently.
Different assets can reuse a ticker and one asset may trade on several networks or venues. Keep an internal asset identifier separate from the exchange symbol; capture network or contract information where it is needed to resolve ambiguity.
Specify whether the deployment covers spot, derivatives, reference indices or token-specific metrics. Data availability and redistribution rights are confirmed per source; a broad asset label is not a coverage or licensing commitment.
Bring the proposed instrument list, source documentation and consumer workflow to a technical discussion. The agreed integration specification defines coverage, fields, usage permissions and acceptance tests.
| Instrument scope | Identify the exact underlying, source identifier, quote currency and intended use. |
|---|---|
| Consumer workflow | List trading platforms, charts, risk tools and applications that need the output. |
| Delivery contract | Agree protocol, quote fields, timestamps, source status and recovery behaviour. |
| Production review | Confirm source rights, integration ownership, test evidence and commercial scope. |
For digital assets, define who consumes the prices and what each system needs to reconstruct a usable quote. An application dashboard, broker platform and historical process can require different delivery rules even when they share one normalized instrument model.