Wow… 😂😂😂

The 80 byte OP_RETURN limit is a relay standard, not a consensus rule. Nodes can set their own limit easily (-datacarriersize flag in Bitcoin Core). This means that nodes (including mining pools) are free to adjust their own relay limits on OP_RETURN size, if they want to be non-standard. tl;dr: You are free to make up your own byte limit but noone else has to "comply" with it.

Only 80 are usable for data though, as the first three bytes are the output header.

It's how it works. Broadcast the rules you agree with. If it gets added to the chain with the most accumulated proof of work, then it's bitcoin.

Someone's lying to you Core changed theirs to 80, but 40 is what the standard was. If they don't want to comply, that's fine, but blaming me for their decision not to is dishonest.

Also note that having ANY extra data hurts your privacy, which seems to contradict the goals of coinjoins. Not really sure what Samourai is thinking here ...

42 is 40 + 2 opcodes (which are counted in the current versions) If you think Core gets to just dictate things, get over your centralization mindset. Knots has used 40/42 since 2013. Samourai are the ones who chose to exceed it.

👍👏🧡😊

Seems this is not a mistake, @jack 😬

Quick question, why is it so hard to change it to 80 and stop the drama? 🤷🏻

80 isn't justifiable, and brc20 spam is at 45

I see, what about leaving it at 44? 😅

Why bother?