1. Luke Dashjr, a Bitcoin Core developer, addressed the OP_RETURN debate, dating back to 2014.
2. Bitcoin Core 0.9.0 introduced OP_RETURN to deter severe spam by limiting data carrier size to 40 bytes.
3. Later, the default size was increased to 80 bytes, maintaining the goal of creating provable, trimmable outputs.
4. This increase aimed to minimize damage from abusive data storage schemes.
5. Dashjr highlighted technical reasons for keeping the lower default value in Bitcoin Knots.
6. There's no intention to filter coinjoin transactions, crucial for enhancing Bitcoin's privacy.
7. Properly constructed coinjoins can adhere to OP_RETURN limits without needing OP_RETURN data.
8. Dashjr's team is open to collaborating on a solution for Knots v25 marking some coinjoin transactions as spam.
9. Cooperation aims to address the recent issue without compromising privacy tools like coinjoins.
10. Dashjr's commitment involves utilizing team resources sincerely for developing a resolution.
