[Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?

Posted by Tom Harding

May 9, 2023/15:21 UTC

The Bitcoin mempool has been experiencing massive congestion due to side projects such as BRC-20, which have a high volume. This threatens the smooth and normal use of the Bitcoin network as a peer-to-peer digital currency. The suggestion was made to reject any transaction where the fee is higher than the sum of the outputs. However, Michael Folkson argued that this would prevent perfectly reasonable transfers of value and attempted Lightning channel closes during fee spikes. He suggested that a transfer can only be reasonable when off-chain value is attached to the coins. A rule like this is the embodiment of the philosophy that the Bitcoin network is for onchain-economic transactions. Parties could get around the rule by paying miners off-network, and that would be an appropriate penalty for using non-onchain-economic transactions. Ali Sherief suggested that we need to find a solution for this that fits everyone's common ground. We indirectly allowed this to happen, which previously wasn't possible before. So we also have a responsibility to do something to ensure that this kind of congestion can never happen again using Taproot.

Link to Raw Post
Bitcoin Logo

TLDR

Join Our Newsletter

We’ll email you summaries of the latest discussions from high signal bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.

Explore all Products

ChatBTC imageBitcoin searchBitcoin TranscriptsSaving SatoshiDecoding BitcoinWarnet
Built with 🧡 by the Bitcoin Dev Project
View our public visitor count

We'd love to hear your feedback on this project.

Give Feedback