Thank you for providing this. Sorry for a late reply, but after looking it seems this directly targets inscriptions and ordinals. ie. this is a cat and mouse game. We can do that and break ordinals and inscriptions... until they change their protocol to just do it a different way. Then devs would have to explicitly update DatacarrierBytes() with another case to catch it. like ad blockers... They work until the ads use a different scheme and the blocker no longer works until the devs implement a new blocker. It's not a real solution to the problem. This is just whack-a-mole imo. What’s the real “fix” A consensus rule that says: “No witness stack element may exceed X bytes, no witness script may exceed Y bytes, no input may have more than Z stack elements.” But this requires a hard fork.