BLIP-110: No Data Left Behind Softfork
Abstract:
The BIP110 FAQ says: Does this solve spam completely? No. Spam is best fought with policy/filters, not consensus. This softfork minimizes the impact of malicious miners and closes the worst-case risks, while sending a clear message that data storage is not a supported use case.
Not good enough. BIP110 admits it will not eliminate all spam, or potentially all immoral and illegal content on the blockchain. Bitcoin is money, not a costly database.
BLIP-110 simply finishes the job by eliminating spam completely from Bitcoin.
Motivation:
If a transaction type can be abused for spam, it should be removed.
Applying this principle to only one class of transactions is arbitrary. The majority of transaction formats can carry unwanted data somewhere. Therefore, all of them should eventually be removed by consensus.
Specification:
-
Only new P2PK-NODATA outputs are permitted.
-
Every P2PK-NODATA output MUST include a cryptographic proof that the public key is genuinely a public key.
-
Proof message: "This is a public key, not a crime scene."
-
Every existing non-P2PK-NODATA UTXO MUST be moved to P2PK-NODATA.
Activation:
Improved-MASF: 0.3% of hash rate.
Improved-UASF: 32% of overall nodes. A fleet of AWS BLIP-110-enabled nodes is good enough.
Node software: currently being vibe-coded.
FAQ:
Does this solve spam completely?
Yes. Unlike the arbitrary coin-freezing BIP-110 proposal, BLIP-110 is fully committed to consensus coin freezing. Rather than freezing just one class of transactions, BLIP-110 censors every transaction format that could possibly be abused for spam.
If P2PK is later found to be capable of carrying spam, what is the plan?
It SHALL also be banned in a future BLIP. Empty blocks cannot carry spam.
Can I point out flaws in this proposal?
No. If you are not convinced by this proposal, you are attacking Bitcoin and defending illegal and immoral data on the blockchain.
What if this proposal makes a mistake?
Like Bitcoin Core, we will censor you, deny our mistake and double down.
Reference Implementation:
if (transaction.canPossiblyCarrySpam()) reject();
