Corrections & Right of Reply

If you are the subject of a report, a reader who has spotted a factual error, or someone who has additional on-chain evidence that bears on a published finding, this page explains how to have it reviewed.

How to submit a correction

Email cryptokarl013@gmail.com with the subject line:

Correction: Report #<number> - <one-line summary of the claim you are disputing>

Please include:

1. The specific claim you believe is inaccurate, copied verbatim from the report.
2. Your evidence - a transaction hash, a filing reference, a PDF, an archive.org snapshot. Evidence that is itself verifiable on-chain or in a public registry is the strongest; evidence that requires trust in the sender alone is the weakest.
3. What you would like the outcome to be - a factual correction, a full retraction, or a right-of-reply response appended to the report.
4. Your identity and relationship to the subject matter. Corrections from anonymous sources are reviewed, but the strongest weight is given to named sources or to the subject of the report themselves.

Review process

• Correction requests are acknowledged within 3 business days.
• A substantive response (correction, rejection with reasoning, or request for further evidence) follows within 14 calendar days.
• If the review establishes that a specific claim is inaccurate, the report is updated with an “Update [ISO date]:” block at the top; the original text is not silently edited.
• If the review establishes that a central finding of the report is wrong, a retraction notice replaces the report body. The URL stays live so that readers arriving from cached links see the retraction, not a 404.
• If the review declines to make a change, the requester may submit a right-of-reply statement for inclusion at the end of the report.

Right of reply

Any named individual or entity that is the subject of a report may submit a right-of-reply statement for publication. The terms:

• The reply will be published at the end of the report in a clearly demarcated block labelled “Response from [name]”.
• The reply must be factual and non-defamatory toward third parties. The site reserves the right to decline replies that contain accusations against third parties unsupported by the reply itself.
• The reply is published in full, up to 800 words. Longer replies are linked rather than embedded inline.
• The site does not edit the reply for tone; editing is limited to obvious typos and formatting.
• Publication of a reply is not contingent on the author’s agreement with it.

What does not qualify as a correction

• Requests to remove a report because it is unflattering, without evidence that a specific claim is factually wrong.
• Requests to remove on-chain evidence because the wallet has since been emptied, renamed, or transferred - the historical transaction record is permanent and public.
• Requests to remove corporate filings citations because the filing has since been amended - the original filing remains on the public record.

For these, a right-of-reply response is available.

Additional evidence from third parties

If you have on-chain or public-records evidence that extends an investigation (additional wallets in the same cluster, further transactions, related entities), please send it via the same address. Useful submissions are credited in the report if you consent to being credited.

Response preservation

When a subject of a report contacts the author with a response but does not consent to publication, the fact that a response was received is still noted on the report (without disclosing its content), so that readers know the subject was given an opportunity to reply.

If you prefer not to use email

The same submissions can be sent via:

• X (Twitter) DM: @CryptoKarl013
• Telegram: @cryptoinvestigations013

Email is preferred because it preserves the record.