"... the demand for inscription incentivized people to build private bridges to miners to bypass other standardness limits such as the maximum transaction size in order to store even more data." "While these restrictions are not binding anymore for whoever wants to store data onchain, they still unnecessarily restrict constructions with time-sensitive transactions. Protocol designers want those transactions to be standard for a good reason: they don’t want to rely on private bridges for security-critical transaction broadcast. Those transactions need to relay properly on the more censorship resistant public network. It was recently brought to my attention that Citrea faced this situation with their Clementine bridge." source:

Replies (2)

or maybe you are falling for the gaslight I guess I will never know. the problem is what Antoine, a core dev said was exactly what ended up happening a change in the op_return and so happens that it was what Citrea needed, and guess what, his rationale makes sense and the solution makes sense, and there were other solutions or approaches. Maybe if this were clear and transparent from the start people could discuss what actually matters, the citrea use case. Instead Core is gaslighting everyone that it's about slipstream, or fee predictions or the best one, mempool consistency lmao.