Audit a crypto white paper's credibility claims
Extract the factual assertions about people, clients and institutions before evaluating the technical narrative.
- Cited claims
- 3
- Source records
- 3
- Edition revision
- 2
In this investigation
Make a claim inventory
Practical checklist · not an audit of another provider
List named customers, partners, licences, executives and completed milestones separately from future plans. Record page references and the document version. Statements such as intends to build and has deployed describe different stages. Keeping them separate prevents a roadmap from being mistaken for evidence of a working product.
Check the external assertions
Practical checklist · not an audit of another provider
Use the named organisation's own records or independently obtained contact details to verify the relationship. A testimonial appearing only on the project's site is not independent corroboration. The Titanium case demonstrates that fabricated social proof can sit beside detailed technical writing. If a claim cannot be checked, label it unresolved and explain which evidence is missing.
Review the money questions separately
Practical checklist · not an audit of another provider
Identify the entity raising funds, the intended uses and the stated custody or spending controls. A technically coherent document does not validate those controls. The FCA's clone-firm guidance also cautions against relying on copied registration details. Preserve the version you reviewed so that later changes to claims, team members or promised uses can be compared accurately.
Annotate a white paper by claim type
Practical checklist · not an audit of another provider
Mark each material statement as a technical proposal, existing product claim, partner claim, financial promise or intended use of funds. For each, record the evidence needed and the source actually supplied. A proposal should not be labelled delivered; a testimonial controlled by the issuer is not independent partner confirmation. Save the document version and date so removed claims remain traceable. Keep unanswered questions in the register instead of filling them with a technical opinion about a different part of the paper.
Sources, dates and limits
Checked 23 October 2026 against the criminal sentencing release and the reproduced signed court order. The signature date is 17 February; the hosting site's metadata says 20 February. The order, rather than the publisher's case summary, controls the account here.
Evidence & sources
- Adjudicated finding
DOJ's March 2023 record reports Michael Stollery's sentence and describes falsified white papers, fake testimonials and false business-relationship claims in the TBIS offering.
Supporting excerpt: CEO of Titanium Blockchain Sentenced for $21M Cryptocurrency Fraud Scheme
planted fake client testimonials
CEO of Titanium Blockchain Sentenced for $21M Cryptocurrency Fraud Scheme ↗ - Source reported
The FCA warns that clone firms can copy genuine registration numbers; checking the number alone is insufficient.
Supporting excerpt: FCA issues warning over ‘clone firm’ investment scams
Scammers will often copy FRN numbers
FCA issues warning over ‘clone firm’ investment scams ↗ - Adjudicated finding
A final civil judgment signed on 17 February 2026 orders Michael Alan Stollery to pay $142,268.10 in disgorgement and $46,888.46 in prejudgment interest, deemed satisfied by the $5,439,462.20 restitution order in his criminal case. Adding those amounts as wholly separate payments would misread the order. The judgment also imposes injunctions; its terms should be distinguished from the March 2023 prison sentence.
Supporting excerpt: US District Court final judgment as to Michael Alan Stollery, signed 17 February 2026 (excerpt)
Dated: February 17, 2026
US District Court final judgment as to Michael Alan Stollery, signed 17 February 2026 (excerpt) ↗