|
|
Edited by Kapil334 at 22-12-2023 05:14 AM
On December 9th, Bitcoin Core developer Luke Dashjr posted on social media, stating that ""the OP_RETURN discussion is not new and can be traced back to 2014 when Bitcoin Core 0.9.0 was released, which included the OP_RETURN policy aimed at preventing more malicious forms of spam. At that time, 40 bytes were the default maximum data carrier size implemented by all nodes; this was sufficient then and now for binding data to transactions (hash value 32 bytes, unique identifier 8 bytes). The subsequent decision by the Core to increase the default value to 80 bytes was entirely voluntary and never contradictory to the design goal of creating OP_RETURN outputs that are provably trimmable to minimize the damage caused by data storage schemes, which have always been considered abusive behavior. There are other good technical reasons, and I choose to keep the lower default value of Bitcoin Knots, and there is no reason to increase it.
Luke Dashjr stated that he and the OCEAN team have no intention of filtering CoinJoin transactions. These provide an innovative tool to enhance Bitcoin privacy, and when constructed correctly, CoinJoins can easily stay within the OP_RETURN limit (in fact, they have no reason to have any OP_RETURN data at all). He has some ideas on how to address the recent issue, where some CoinJoin transactions are flagged as spam by Knots v25, and is willing to leverage his and his team's resources to sincerely collaborate on developing a solution. |
|
Post time 13-12-2023 20:45:16