Ironically you are actually making both sides of the argument here.
One potential reason for removing the op_return limit is so data can be added to the blockchain in the least obtrusive way. Anchor data, or the hash of a file for example. (Related to what you're suggesting) And op_return is the best place to do this. Currently spammers are just jamming data into the witness area which is objectively worse.
On the other hand enabling unbounded data in transactions is arguably not what bitcoin is for.
And there is much nuance in the arguments as you dive in really...
Thus the drama.
m0053
npub1qk…x9qas
2025-05-02 09:33:01
in reply to nevent1q…pdcr
Author Public Key
npub1qktjyk0vdqlfss7wztawdnka5phx2p3vlvq50x0z402jk2fjhtnqlx9qasPublished at
2025-05-02 09:33:01Event JSON
{
"id": "31b814739116d067f3981b52f8924ba0ae9c36bf526b71c6bf238c3c2320b7b2",
"pubkey": "05972259ec683e9843ce12fae6cedda06e65062cfb014799e2abd52b2932bae6",
"created_at": 1746178381,
"kind": 1,
"tags": [
[
"e",
"c5b07fb3bb6a1f747c499ff547f20f4d944d328f07f7b23a3eafa4c151e117a1",
"",
"root"
],
[
"p",
"57421efdd7ccc45af8c5ff8c9f9f2281a671d8f0049c9dfbff214f2928b4a3af"
]
],
"content": "Ironically you are actually making both sides of the argument here.\n\nOne potential reason for removing the op_return limit is so data can be added to the blockchain in the least obtrusive way. Anchor data, or the hash of a file for example. (Related to what you're suggesting) And op_return is the best place to do this. Currently spammers are just jamming data into the witness area which is objectively worse. \n\nOn the other hand enabling unbounded data in transactions is arguably not what bitcoin is for. \n\nAnd there is much nuance in the arguments as you dive in really... \n\nThus the drama.",
"sig": "20020c301a52e47ee4619270b444a6a3168553a9203ab6b555d9fbbbf54035f15da5e8d636d3baa0a1b12839842cebffafb5637c718adf6caa95c9c0336d73cc"
}