According to Foresight News, Bitcoin Core developer Luke Dashjr has addressed the ongoing debate surrounding OP_RETURN, stating that the discussion is not new and can be traced back to 2014. At that time, Bitcoin Core 0.9.0 was released, which included the OP_RETURN policy aimed at preventing more severe forms of spam. The default maximum data carrier size limit for all nodes was 40 bytes, which was and still is sufficient for binding data with transactions (hash value 32 bytes, unique identifier 8 bytes). The core later increased the default value to 80 bytes voluntarily, without contradicting the design goal of creating provable, trimmable outputs with OP_RETURN to minimize damage caused by data storage schemes, which have always been considered abusive.
Dashjr also mentioned that there are other good technical reasons for retaining the lower default value of Bitcoin Knots and that there is no reason to increase it. He and the OCEAN team have no intention of filtering coinjoin transactions, which provide an innovative tool for enhancing Bitcoin's privacy. When constructed correctly, coinjoins can easily stay within the OP_RETURN limits and have no reason to possess any OP_RETURN data.
Dashjr expressed his willingness to use his team's resources to sincerely cooperate in developing a solution to the recent issue of some coinjoin transactions being marked as spam by Knots v25.
