The Bitcoin network, known for its robust security and efficiency, is now contending with a new challenge: spam transactions driven by profit. Unlike traditional spam, which generally involves low-value or nuisance transactions, this new breed of spam—characterized by Ordinals, Inscriptions, BRC20 tokens and Bitcoin Stamps—is created with a clear profit motive, complicating the issue further.
The Profit-Driven Nature of New Spam:
Why This Is a Major Concern:
Protocol Exploitation: Bitcoin's design is intended to limit extra data on the blockchain. Spam transactions exploit code rules to sell data within arbitrary transactions.
Increased Fees: Higher congestion leads to increased fees, pricing out regular transactions.
Shift Away from Bitcoin’s Core Purpose: The rise of profit-driven activities challenges Bitcoin's original intent as a decentralized financial platform.
Imbalance of Incentives: Miners Benefit, Users and Node Operators Bear Costs
Miners profit from higher fees associated with these transactions, while regular users face inflated costs for standard transactions. Node operators are burdened with storing and processing arbitrary data for completely other usage, which never had any consensus from participants. This shift undermines the network's fairness and incentive balance.
Addressing the Challenge:
A recent Twitter conversation underscores the effectiveness of mempool filters in managing spam transactions on the Bitcoin network. This discourse involved key Bitcoin community members and developers, illustrating the real-world implications of mempool filters.
https://twitter.com/francispouliot_/status/1743704660123308387
In the conversation, Ben Carman (@benthecarman) expressed his skepticism about the efficacy of spam "filters". This was followed by Francis Pouliot (@francispouliot_), who requested a 100 sat transaction to a specific address. Rob Hamilton (@Rob1Ham) responded with a transaction hash but, as ndgo (@ndgoHODL) pointed out 10 hours later, the transaction had still not appeared in the mempool, leading to speculation about the transaction's nature and destination. The reason the transaction did not process is because such small transactions are excluded by the standard Bitcoin Core mempool filters.
This example demonstrates that despite the skepticism, mempool filters can effectively distinguish and manage different types of transactions. Rob Hamilton's transaction not appearing in the mempool even 24 hours later, despite a clear hash being provided, indicates that mempool filters are functioning in discerning and controlling these transactions.
The goal should be to encourage Bitcoin Core to refine these existing mempool filters further to ensure that such spam transactions are systematically excluded from the mempool. This should help deal with the bulk of spam and improve the network's efficiency and realign with Bitcoin's core purpose.
datacarrier=0
in the bitcoin.conf file of your Bitcoin Core node instance to prevent spam transactions from entering your mempool.