TokenScouts is a personal research project by a crypto enthusiast, using AI tools to help organize public sources and explain products. It is not a staffed newsroom, audit firm or product-testing laboratory.

TokenScouts turns crypto claims into checkable evidence: dated Risk Passports, source-level verification, and change tracking. This page explains what you see on a review, what each status means, and what we do not claim.

We explain how a product works, what can go wrong, and what remains unverified. Nothing here is financial advice or a recommendation to buy, sell, or hold any asset.

What the blocks mean

Structured evidence on a review is separate from the editorial article. Labels map to on-page anchors:

  • Risk Passport (#risk-passport) — a compact due-diligence card: passport status, open-model score, coverage, watchouts, and unknowns. Not a price forecast.
  • Sources (#evidence-ledger) — the evidence ledger: each row is a fact, its value, how strongly we trust it, and where it came from.
  • Checks (#hands-on) — desk checks against public pages and repos; hands-on device/account tests stay Not run until we actually perform them.
  • Incidents (#incidents) — curated incident notes with sources. A starting checklist, not a complete history. Missing entries are not proof of safety.
  • Research (#research-notes) — short automated notes from public GitHub releases for the linked repository. Useful signal, not a rewrite of the review.
  • What’s new (#whats-new) — bounded updates when tracked evidence moves. Only the marked update section is replaced; the rest of the article is not silently rewritten.

Fact status meanings

Every Sources row carries a verification status:

  • Verified — cross-checked, or backed by a primary/trusted source we accept for that field.
  • Observed — seen in a source, but not yet at our verified bar. Volatile market figures often stay observed until a second source exists.
  • Conflict — sources disagree. Treat with extra caution until resolved.
  • Stale — older than our freshness window for that field type. May still be directionally useful.

Passport status meanings

  • Tracked facts checked — the status previously labelled Verified. It refers to the limited tracked field set, not a product safety assessment or a completed hands-on test.
  • Some tracked facts checked — useful source data exists, but tracked fields or checks remain incomplete.
  • Limited tracked evidence — the model has too little source data to support a full card. Missing facts do not establish that the product is unsafe or safe.

The evidence score is 0–100 from a versioned rules model. It summarizes coverage, source quality and selected signals. It is not a probability of safety, a security audit, a solvency opinion or an investment recommendation. Coverage of 100% means the limited tracked field set is filled, not that fees, KYC, custody and security were all assessed.

What the score can and cannot show

Scores are computed by a versioned rules file per entity type (coin, wallet, exchange), not by an LLM choosing a number. Same inputs produce the same outputs. For exchanges, the currently documented field set covers third-party trust metrics, trading volume and establishment year, with country as an optional field. These inputs do not establish reserves, withdrawal reliability or regulatory eligibility. For wallets, repository activity or documentation reachability does not establish secure device operation. A numeric score is only a summary of the inputs it actually measures.

Writers may explain verified facts. Automated critics block unverified claims and investment hype such as guaranteed returns.

Not financial advice

TokenScouts is due-diligence research for ordinary readers. We do not promise safety, returns, or regulatory outcomes. Always verify primary sources linked on each page and follow the laws that apply to you.

What auto-update does — and does not

Does: refresh API observations into the evidence store; re-check conflicts; recompute open-model scores; refresh on-page evidence blocks from caches; update the bounded “What’s new” section when material signals change under the site’s publication policy. Editorial updates can also be published after the configured checks; their date is shown on the page.

Does not: invent hands-on results, turn a blocked documentation request into a failed product test, or treat a populated data card as a completed editorial review. Our curated incidents catalog is not a complete history.

Hands-on honesty

  • Desk — checked from public documentation or URLs without creating an account.
  • Hands-on — requires a real product run (device, signup, deposit, withdrawal, and similar). We leave these Not run until TokenScouts records a real result. We never invent them.

Corrections

When a fact or score was wrong, prefer a dated note in What’s new / Sources over a silent overwrite. Methodology and model versions are recorded with the evidence pipeline.

Methodology updated October 22, 2026. Sources and testing limits matter more than a numeric score.