Post
Topic
Board Development & Technical Discussion
Merits 4 from 3 users
Re: Removing OP_return limits seems like a huge mistake
by
NickofTime
on 06/05/2025, 21:29:52 UTC
⭐ Merited by ABCbits (2) ,vapourminer (1) ,JayJuanGee (1)
A bit late to the party. I don't know if removing the filter was a mistake, this only time will tell. A few things on my mind:

Motivation: this was not properly addressed. From this discussion alone it seems that the choice of imposing no limit on OP_RETURN was for the benefit of the network. This is not what happened. This is not why the pull request was made. I refer you to a post by Peter Todd himself on stacker.news

Quote
For the record, this pull-req wasn't my idea. I was asked to open it by an active Core dev because entities like Citrea are using unprunable outputs instead of OP_Return, due to the size limits. And yes, that's the thing that has changed since.
https://stacker.news/items/971277?commentId=971434

Was this really for the benefit of the network or for the benefit of Citrea? Why did this anonymous developer go through Todd for the PR? Am I the only one seeing red flags here?