Read the source in context
Official project sources show the publisher's own statements. Several documents from the same publisher are not automatically independent confirmations. Check who is speaking and what the referenced passage supports.
A selection of material
The available evidence is a selection, not the whole internet or everything about a project. The introduction is public. Further material follows your account access; any published saved examples have their own stated scope.
Different dates mean different things
Publication date tells you when the source was published; collection time tells you when we collected it. A measurement or event time describes when an observation or event applies, if the source states it. Checking the same text again is not a new network measurement. A missing time remains unknown.
Does the answer address your question?
Read what the references support and what the answer actually addresses. A supported fact can answer only part of a broad question. A coverage label is not a guarantee of relevance or a complete project description.
Preserved material and current access
A link opens the source as it is now, not necessarily the version we preserved. Today, you can read the material made available within your account access; preservation alone does not make every earlier version accessible. Historical comparisons and new project charts are under development and are not yet part of the customer view. Preserved text alone does not explain why something changed.
When evidence is insufficient
An unanswered question describes what the service could provide for that question. It does not mean the information is absent everywhere or that the project is poor. A technical error is a separate situation; follow the retry guidance shown.
Status is not a quality guarantee
Read the status supplied for a statement and its limits. Publication and human content review are different things. A published statement does not establish that every claim is true or independently confirmed.
No one can buy a place in the catalog, its ordering or a Trust Score. The planned Verification charges for the review work, but payment never grants approval.
A timestamped evidence chain
Every night, TrustDePIN combines all new snapshots and receipts into one Merkle root. DigiCert and Sectigo timestamp it independently under RFC 3161, and OpenTimestamps anchors it in Bitcoin. For timestamping, only a fingerprint is sent — no project content and no customer data. Later changes are detectable.
How to verify the evidence chain · Verification log
A statement, its source and its limits
- Statement to examine
Describe the exact claim and who makes it.
- Source
Open the relevant source and read it in context.
- Time context
Distinguish publication, collection, event and review dates. Leave missing dates unknown.
- Limitation
State what the source supports and what remains uncertain.
Use the project catalogue to apply this reading method to published introductions.
Explore project overviews
See how the planned DePIN verification (beta) will document scope and evidence.
Corrections and editorial responsibility
TrustDePIN maintains these public introductions. To request a correction, include the project, the wording concerned and a supporting source.
Contact TrustDePIN
Explore project overviews →