How to Build a Source Hierarchy for an RWA Profile
A neutral structure for separating issuer documents, dashboards, legal pages and secondary coverage.
This article may contain affiliate links. Commercial relationships are disclosed in the affiliate policy.
An RWA profile mixes documents of very different authority, and reading them at equal weight is what produces confident errors. A source hierarchy fixes the order before you read anything.
Rank sources before you collect them
Decide the ranking first, then gather material into it.
The usual ordering starts with issuer legal and offering documents, moves to on-chain records, then regulatory filings, then dashboards and analytics sites, and ends with news coverage and commentary.
This order is not a quality ranking of writing. It is a ranking of what settles a question when sources disagree.
A dashboard number is easier to read than a legal document and is far easier to read wrong. Convenience is not authority.
Tier one: issuer and legal documents
These are the documents that create the claim in the first place.
Offering memoranda, subscription agreements, terms of service, and the legal entity’s own disclosures describe what the token represents and what obligations attach to it.
Read for the specific question rather than the whole document. The sentence that defines the redemption process matters more than the section on marketing restrictions.
Two details deserve special attention because they are commonly stated vaguely: what entity holds the backing, and under what conditions a holder can redeem.
Tier two: on-chain records
The chain shows what actually happened, which is not always what a document described.
A reserve attestation is a claim about a balance. A balance visible at an address is the balance itself. Where the two disagree, the disagreement is the finding.
Record the block height for every on-chain figure you cite. A balance read at one height is meaningless without the height, because tokenized asset balances change continuously as tokens are issued and redeemed.
Tier three: regulatory filings
Filings tell you how an asset is classified, which determines what restrictions apply to who may hold it.
Regulatory status is also the fastest-moving part of a profile. An offering that was restricted to accredited investors may have changed, and a dashboard rarely updates that field as promptly as the filing does.
Tier four: dashboards and analytics sites
Dashboards are genuinely useful and easy to overuse.
They aggregate many sources, which means they inherit every ambiguity in the sources beneath them. A category total assembled from several issuers may count assets that share a wrapper but not a structure.
Use dashboards for scale, for comparison across assets, and for noticing that something changed. Use them to identify what to verify, not as the final word on what is true.
A dashboard figure should always carry the date and time it was retrieved, because these pages refresh continuously and an undated number cannot be checked later.
Tier five: news and commentary
Coverage is where most RWA profiles get their framing, and framing is the thing to be most careful about.
Headlines routinely compress a filing into a stronger claim than the filing makes. Coverage is also the tier most exposed to promotional pressure, since many issuers run paid campaigns.
Treat a news article as a pointer to the document behind it. Follow it to tier one or two. If no document can be found, the claim has not been established, however widely it has been repeated.
Resolve conflicts by rank, not by vote
When two sources disagree, the higher tier wins, and you record the conflict rather than deleting the losing source.
A single legal document outranks ten dashboards. Three news articles citing the same press release remain one source, not three.
Recording the conflict has lasting value: a discrepancy between an attestation and an on-chain balance is often the earliest visible sign of an operational problem.
Write the hierarchy into the profile
A profile that never states its source order will be rebuilt from scratch by the next person who reads it.
Include a short section naming each tier, what it can settle, and what it cannot. Note the retrieval date next to every figure.
When a profile cites a dashboard number without noting that it came from a dashboard, a reader cannot tell which claims were verified and which were aggregated.