The limit was removed because it is an arbitrary-volatile policy rather than a consensus rule. In any case, various wallets began to avoid, and it was the “relay policy” that led to contradictions. Changes to V30 simply align the Bitcoin Core default policy with what is actually happening.
The impact was discussed, but the view of the developers who integrated it was that node operators who were concerned about chain bloating had always had the ultimate tool and had the ability to set their own, more stringent policies. This change will force no one to accept these transactions. Just change the defaults.
The original compromise came from a time when the threat of spam was seen differently. This update reflects a practical shift, acknowledging that data use cases exist and that attempting to suppress them in one policy is less effective than individual node operators being able to choose their own limits.
Discover more from Earlybirds Invest
Subscribe to get the latest posts sent to your email.
