Quote from: pooya87 on Today at 02:39:12 PM

Or this limit existed in Bitcoin Knots for a very long time (maybe from the very beginning) and is not a new thing this implementation of the protocol is enforcing as standard rule. Here is a random oldest version I could find from 8 years ago with the 42 byte limit present:
https://github.com/bitcoinknots/bitcoin/blob/v0.12.1.knots20160629.rc2/src/script/standard.h#L30

Huh... I stand corrected. Apologies.

So the timing of this is just a super bizarre coincidence? I'm really confused now.

Still, it highlights the importance of how careful we have to be. If clients are disregarding certain transactions when devs aren't even trying to crackdown on ordinals, imagine the potential for mistakes when they are trying and start making deliberate changes.

Particularly when it comes to coinjoins. In this current climate, when we're attempting to shift attention away from centralised mixers, we have to do everything possible to nurture and encourage coinjoins. We absolutely do not need the drama of such transactions being blocked right now. The timing of this really is unfortunate.

I still urge the angry mob to put down their pitchforks and torches and pause to consider the ramifications here.