"Revealed preferences" cuts both ways. Core revealed they prioritize hypothetical corporate use cases over 93 node operator NACKs. That's the capture.
Whether Citrea bothered to adopt it is irrelevan...
"the policy was changed because of their business model"
no, that's a non sequitur. the policy was changed because core devs understood that there is a gap between the old OP_RETURN limit and what is economically rational to inscribe in witness script (commit-reveal). between 80 bytes and like145 bytes or something it was "economically rational" to use fake outputs. they didn't like this realization.
citrea was definitely used as an example in their debates tho. the reason they gave for not putting a new cap on OP_RETURN is very weak and self contradictory tho. that's why i said it was an error imo.
no, that's a non sequitur. the policy was changed because core devs understood that there is a gap between the old OP_RETURN limit and what is economically rational to inscribe in witness script (commit-reveal). between 80 bytes and like145 bytes or something it was "economically rational" to use fake outputs. they didn't like this realization.
citrea was definitely used as an example in their debates tho. the reason they gave for not putting a new cap on OP_RETURN is very weak and self contradictory tho. that's why i said it was an error imo.