Bitcoin Core v30, released recently, removed its spam filter, reigniting an old debate that now threatens to split developers, spark a soft fork, and draw in big names like Michael Saylor.
On Oct. 24, two weeks after the action of Bitcoin Core v30, GitHub user Dathonohm introduced a pull request with Bitcoin Improvement Proposal 444. BIP-444 proposes a soft fork restricting adding non-monetary data (texts, images, etc) to the Bitcoin blockchain for one year.
The description explains that the proposal is aimed at overcoming Bitcoin’s identity crisis in 365 days:
As for the argumentation, Dathonohm repeats all the same reasons that have been circulating on Crypto X after the spam filter removal in Bitcoin Core v30 was announced.
Dathonohm and the BIP-444 supporters in the comment section name the following:
The two camps see the initial purpose of Bitcoin differently. The Knots and BIP-444 proponents believe Bitcoin is an electronic cash system; thus, they don’t want non-monetary data on the blockchain. They suggest that opening gates to illegal images threatens the well-being of Bitcoin’s primary use as a monetary system.
The Bitcoin Core supporters argue that Bitcoin should not always try to catch up with the law, as it was initially built as an alternative to any government. Moreover, they see neutrality in allowing any kind of data to be stored on Bitcoin. There is no “wrong” way to use Bitcoin, in their opinion. Some of them see a soft fork as too serious a change, no matter if it’s only for a year.
Many in both camps insult and troll each other online. They call each other “communists.” Bitcoin Core supporters think that the Knots camp is trying to suppress freedom of expression and censor Bitcoin. Knots and BIP-444 proponents see Bitcoin’s non-monetary use as an attack on financial freedom.
In September, not long before the adoption of Bitcoin Core v30, the founder of MicroStrategy (now called Strategy), Michael Saylor, voiced his concerns over spam data. He noted the following:
Saylor’s remarks didn’t influence the situation, and Bitcoin Core v30 was released as planned.
The Bitcoin Core team didn’t explicitly change the protocol. They didn’t remove the spam filter altogether. Rather, they gave users an option to regulate it. By default, the arbitrary data carrier now has a 100,000-byte size, which is way higher than the 83-byte limit. Allegedly, most node runners don’t change it.
However, one month into the use of Bitcoin Core v30, there is no evidence that Bitcoin has changed. Probably, initiatives coming from the limitless, arbitrary data carrier will follow soon. It is too early to judge how they will impact the network. As of the press time, Bitcoin is alive and well, and the main damage was done to the community spirit.


