-
@ Dikaios1517
2025-05-12 06:49:46
Guy Swann had a very balanced take on the whole debate here: https://fountain.fm/episode/twR9XdpCO0yoMTSQUGPj
Gist of it is that the reasoning behind removing the datacarrier limit for OP_ RETURN is sound, but the devs should not have been surprised that it would be controversial, and Core has generally avoided making controversial updates. It probably also wouldn't have been nearly such a big deal if they left it configurable, but their plan is currently to remove the option to configure it.
Meanwhile, Knots is keeping it configurable. You can run knots with no limit on the datacarrier size if you want, or you can leave it at the default 40 bytes, or you can set it to Core's current default. Point is, you have options with Knots that Core is planning to take away.
One of the arguments made by the folks supporting the change to Core is that OP_RETURN is a far better place for arbitrary data to be stored, because it can safely be pruned by nodes, so they don't have to store that data. However, there is no financial incentive for the jpeg and BRC 20 folks to put their data into OP_ RETURN, because they are currently putting it into the witness data, where they get a significant fee discount. Even if the datacarrier limit is removed, there is absolutely no reason to believe the degens will forego that free discount and start placing their garbage in OP_ RETURN instead.