This is a good one from Bitcoin Core v30 enthusiasts: - "I don't know who needs to hear this, but you can run whatever Node software you like." However, even strict/old nodes still ingest mined bytes. They may refuse to relay big/"weird" txs, but when a block containing that data is mined, all validating nodes download/store it (pruned nodes still transiently process bytes). So liability headlines ("illegal payload on-chain") hit everyone roughly equally once mined. Stricter policy is not equal to legal immunity; looser policy does lower the bar for adversaries. The attack becomes logistically easier (and deniable) when defaults relay bigger payloads. So here is the translated version: - "I don't know who needs to hear this but if Bitcoin Core v30 defaults roll out widely -> you'll be hit with spam/data waves -> bad headlines and regulatory pressure will follow -> then several top pools formalize policy templates; and then app stores/clouds tighten AUPs on non-KYC wallets/nodes. Then, Bitcoin as a MoE becomes more contained, while paper/custodial rails gain share." Well, I don't know who needs to handicap Bitcoin by making these changes. Oh wait, I actually do know. View quoted note →