Bitcoin Developers Discussing Whether to reject non-standard Taproot Transactions from full nodes

Some Bitcoin developers are considering rejecting non-standard Taproot transactions from full nodes in response to recent mempool congestion caused by projects such as BRC-20.

The issue has caused real Bitcoin transactions to be priced out and threatens the smooth and normal use of the network as a peer-to-peer digital currency. While some have suggested enforcing censorship at the node level and introducing a run-time option to instantly prune all non-standard Taproot transactions, others argue that this is a technical issue and not a matter of philosophy or ideology.

They suggest that congestion can happen using Taproot or pre-Taproot addresses due to the fixed, limited block space and variable demand for that block space. While some developers believe that miners are largely at fault for allowing the system to be abused, others argue that miners are simply following the system as it has been set up for them to do. As a result, some suggest that a consensus change or a policy change may be necessary to prevent this kind of congestion from happening again in the future.

TokenInsight is dedicated to covering the most important and cutting-edge trends in the world of crypto. If you have information to share with us, please feel free to contact our email news@tokeninsight.com. Your trust will be well respected.