TechFlow reports, Bitcoin core developer Luke Dashjr stated on Twitter that discussions about OP_RETURN originated in 2014 when Bitcoin Core version 0.9.0 was released, which included the OP_RETURN policy aimed at preventing more severe spam. He noted that OP_RETURN creates provably prunable outputs to reduce potential harm from data storage schemes.
Dashjr explained that his decision to maintain a low default value in Bitcoin Knots, rather than increasing it, is based on technical and design considerations. He expressed willingness to work collaboratively with the OCEAN team to resolve the issue of coinjoin transactions being flagged as spam.
He also emphasized that Bitcoin has always supported node-based filtering, and the default setting in Knots v25 represents what he believes is currently most beneficial for Bitcoin. Dashjr highlighted that OCEAN is moving toward decentralization, and in the future, more participants will be able to independently decide on their node software versions and policies.
