OSINT · 29 January 2026 · 7 min read
Source Verification in Open Source Research
By Digital Asset Claims Research Desk·Investigation Team
- OSINT
- Source Verification
- Evidence Standards
Public availability of information says nothing about its reliability. Source verification is the structured process that separates well-founded findings from material that merely looks credible at first glance.
A claim repeated ten times across ten websites that all copy from the same original post is still a single, unverified claim.

Tiering Sources by Proximity to the Original Record
Primary sources originate directly from the entity or system being examined, such as a raw blockchain record or an exchange's own filed disclosure, and carry the highest evidential weight before further checks are applied.
Secondary sources involve interpretation, such as journalism or analyst commentary, and are useful for context but require tracing back to primary material wherever a specific factual claim needs verification.
Tertiary sources, including forum speculation and social media commentary, are treated as leads only and are never cited as the sole basis for a factual claim in a finalised report.
Dating and Change Detection
Establishing when a claim first appeared, and whether it has since been altered, is central to assessing reliability. Archived snapshots and metadata analysis support this timeline reconstruction.
Content that has been quietly edited after initial publication, particularly to remove or soften a specific claim, is treated with additional caution and documented as such in the case file.
Domain and certificate history provide an independent check on a website's claimed operational timeline, which is useful when a fraudulent platform misrepresents how long it has been active.

Tracing Citation Chains
Multiple reports of the same claim are checked to determine whether they are genuinely independent or whether they trace back to a single upstream origin, such as a shared press release or leaked document.
Where a citation chain collapses into a single source, the claim's confidence rating is adjusted downward accordingly, regardless of how widely it has been repeated online.
This tracing process is time-consuming but prevents a common failure mode in open source research, where apparent consensus is mistaken for independent corroboration.
Documenting Confidence for the Final Report
Each source's reliability assessment is recorded alongside the claim it supports, creating a transparent link between evidence and conclusion that a reader can inspect.
This documentation allows recipients of a report, including legal counsel or platform compliance teams, to form their own view of the material rather than relying solely on the investigator's summary.
Where verification remains incomplete, the report states this explicitly rather than presenting a partially verified claim with unwarranted certainty.
Indicative source tiers used in open source research
| Tier | Example | Typical Use |
|---|---|---|
| Primary | On-chain transaction record, exchange filing | Direct basis for a finding |
| Secondary | News reporting, analyst commentary | Context and corroboration |
| Tertiary | Forum posts, unverified social media | Lead generation only |
| Technical | WHOIS, certificate transparency logs | Timeline and authenticity checks |
Frequently asked questions
What happens if a source cannot be independently verified?
The material is retained in the case file as an unverified lead and is not used as the sole basis for a finding presented in a final report. It may still guide further enquiry.
Are anonymous tips ever used in investigations?
They are logged and can direct further research, but they are treated as unverified until corroborated through technical or documentary means.
Does source tiering apply equally to on-chain and off-chain material?
The principle applies to both, though the specific verification tools differ. On-chain data is verified against the ledger directly; off-chain claims require independent corroboration across sources.
How is a source's history checked for tampering?
Archived snapshots, page metadata and version history where available are compared against the current version of the material to identify any changes since original publication.
Rigorous source verification is what allows open source research to support, rather than undermine, a digital asset investigation. Tiering, dating, cross-referencing and transparent documentation together ensure that a finding's stated confidence genuinely reflects the strength of the evidence behind it.

