Skip to content
← Corpus

Claim

Csam is prevalent on the bitcoin blockchain

NUANCEDmedium confidencedata embedding

Verified as of 2026-07-22. Not re-checked since.

⚠️ Time-sensitive — not re-verified since `asOf` (2026-07-22). The refutation rests on present-tense findings that decay: "no current large-scale CSAM problem attributable to raised OP_RETURN limits or absent filtering," "no evidence as of the source event" that prevalence is high now, and "no demonstrated causal instance as of the source event" of the raised limits producing illegal content. All three were checked against conditions at the December 2025 source event and not since — and the entry's own point is that "is it prevalent now" is a separate question from "has it ever been there," which makes the now the perishable half. asOf records the last verification, not the last edit — any editing since then left the date unchanged because it added no re-verification of the current record. Re-verify against a primary source before asserting on stage that the problem is still absent.

Child sexual abuse material is being stored on the Bitcoin blockchain at meaningful scale as a result of relaxed data limits.

As asserted vs. as found: The prevalence claim circulates as justification for filtering and for consensus-level data restrictions. Independent checking reported at the source event found no current large-scale CSAM problem attributable to raised OP_RETURN limits or absent filtering — the known history is sparse: an encoded image reportedly snuck on chain in 2011, academic work in 2018 documented a small number of objectionable files and links among roughly 1,600 embedded files, and one 2025-era case involved apparently AI-generated imagery. The strongest version of the concern is therefore prospective, not descriptive: the chain can carry such material, every full node replicates whatever it carries, and one well-publicized incident could trigger disproportionate legal and political consequences.

Nuance: "Is it there at all, ever" (yes, in trace historical amounts, mostly as links rather than files) and "is it prevalent now" (no evidence as of the source event) are different questions, and debaters routinely slide between them. Prevalence claims should be treated as unevidenced unless accompanied by specific, checkable findings; risk claims are legitimate but should be argued as risk.

Common misstatements: "The blockchain is full of CSAM" (no supporting evidence; the documented instances are rare and mostly pre-date current limits). "There has never been any objectionable content on chain" (contradicted by the 2011 incident and the 2018 study). "Raising OP_RETURN limits caused illegal content" (no demonstrated causal instance as of the source event).

Sources (2)

  1. 1.The OP_RETURN Saga Continues Live at PubKey NYC Main speakers Arbedout Thomas Pacchia and Andrew NewmanArchived recording, transcript held in-house (not published)

    A speaker who researched the question before the event reported finding no current CSAM problem; the 2011 encoded-image incident and one AI-generated case were discussed

  2. 2.link.springer.comPublished article

    Matzutt et al., "A Quantitative Analysis of the Impact of Arbitrary Blockchain Content on Bitcoin" (Financial Cryptography 2018) — documented objectionable content and links among ~1,600 files found on chain

Related entries