Bitquery’s Sept. 2 census of 965,135 Bitcoin blocks compared four ways text appears on the network and found sharply different effects on node state. It identified 13,062 OP_RETURN taunt transactions across 579 blocks, including a March 21-26, 2026, campaign that named Bitcoin Core developer Luke Dashjr in the same two-sentence taunt. The transactions came from 13,062 sending addresses and paid 0.1014 BTC in aggregate fees. The chain records the text, timing, inputs and fees, but not the payer, author or motive. Across the wider scan, Bitquery counted 4,412,782 readable OP_RETURN outputs. Because OP_RETURN data is not retained in the UTXO (unspent transaction output) set used to verify spendable coins, it expands block history without creating persistent spendable-looking state. By contrast, Bitquery found 96,231 fake-address text outputs across 3,286 transactions, holding about 3.2 BTC that is effectively unspendable while remaining in current node state unless spent. Bitcoin Core 30.0, released in October 2025, raised the default -datacarriersize setting to 100,000 and permitted multiple OP_RETURN outputs under an aggregate relay and mining limit, without changing consensus rules. Longer-than-80-byte messages increased from a few dozen appearances in most pre-v30 months to thousands by February 2026, although the observed sequence does not establish that v30 alone caused the increase. The 62-byte ASCII taunt already fit under the former limit. Bitquery also lacked coinbase fields for 191,427 historical blocks and excluded witness inscriptions, so its study compares the state consequences of four measured channels rather than all text embedded in Bitcoin.