The standard datacarriersize Knots has always used is 42 bytes. They knew that and ignored it. We haven't changed anything in this regard. Brc20 comes in at 45 bytes, so just increasing it isn't a viable solution. That doesn't mean we're giving up - we do want to mine these - but it's going to take some work if Samourai doesn't fix the issue on their end (ultimately there's no good reason for ANY of this data)
Thanks for the response. I am not knowledgeable about datacarriersize. Does this refer to a constant in bitcoind code? Does it only apply to OP_RETURN? I was under the impression that BRC-20 uses the inscription data envelope technique, which does not involve OP_RETURN. That makes me think you are using datacarriersize to refer to the total amount of data you are willing to allow a transaction to store, regardless of the technique used. Can you please clarify this for me?