How Counterparty's Fake-Pubkey Trick Exposed Bitcoin's Consensus vs Policy Divide

Counterparty, launched in 2014, was the first protocol to systematically embed arbitrary data in Bitcoin by encoding payloads inside fake public keys within 1-of-3 bare multisig outputs, bypassing the roughly 80-byte OP_RETURN limit. To do this, Counterparty clients had to 'grind' fake public keys — searching for x-coordinates that both encoded the payload and produced a valid secp256k1 curve point — because Bitcoin Core rejects any transaction containing provably invalid public keys before it even reaches the mempool. This technical constraint highlights a fundamental but often misunderstood distinction in Bitcoin: consensus rules enforce mathematical and script validity for every transaction, while mempool policy rules exist separately to prevent spam and node abuse. Consensus does not judge whether a public key is being used as a data container or whether an output will ever be spent — it only verifies internal script consistency and curve validity. The Counterparty case serves as a historical illustration of how Bitcoin's layered architecture separates value-neutral mathematical guarantees at the consensus level from practical network-health decisions enforced at the policy level.