so the problem is OP_RETURN is one of the issues. core of the issue was 3 years ago, Core didn't patch their implementation against exploits appeared after taproot fork.

so if you are running Core and not updating, you are still running a node that doesn't have patches against taproot exploits. and down the road because of the issues this exploit caused, Core wanted remove OP_RETURN limit.

so you can say they caused the problem to create the "solution".

Reply to this note

Please Login to reply.

Discussion

Yeah, I’m not educated enough on this, just getting the sense that many would rather sweep it under the rug (which is not good if it’s bad and not understood properly, and the default )