I'm sorry to inform you that OP is full of shit. You've been gaslighted. - Op_return is some ways is less harmful than other spam methods. But the spammers would lose the segwit and taproot discounts. So they are not likely to switch to taproot. The coretards told us for 4 years that "the fees are the filter" and they are suddenly ignoring their own bullshit claims when it no longer suits them. - Ordinals are not inevitable. Someone suggested an ordinal filter 2 years ago. Coretards invited a bunch of spammers to bitch about censorship. And they also changed a definition in their documentation. Than they rejected the filter by claiming it's too controversial and based on the new definition they just changed. - We have Taproot and Segwit mainly as scaling methods. They are both good upgrades. But like all code, they come with bugs and exploits. The problem is that core has refused to fix any of the bugs and exploits of Segwit and Taproot. Mainly because they don't think spam is a thing. Murch (core dev) doesn't know what spam is. And Zhao (head dev) calls it "use cases we have today" instead of calling it spam. And she claims Satoshi didn't have the foresight to plan for those "new use cases we have today". That is false. File sharing was NEVER a supported use case of 123b06, until core 30 anyways You could post a file on 123b06 only by obfuscating it to make it look like a genuine 123b06 transaction. Even OP admits thus much. Thought the rest of his childish and ridiculous monster analogy is pure bullshit.
I'm sorry to inform you that OP is full of shit. You've been gaslighted. - Op_return is some ways is less harmful than other spam methods. But the spammers would lose the segwit and taproot discounts. So they are not likely to switch to taproot. The coretards told us for 4 years that "the fees are the filter" and they are suddenly ignoring their own bullshit claims when it no longer suits them. - Ordinals are not inevitable. Someone suggested an ordinal filter 2 years ago. Coretards invited a bunch of spammers to bitch about censorship. And they also changed a definition in their documentation. Than they rejected the filter by claiming it's too controversial and based on the new definition they just changed. - We have Taproot and Segwit mainly as scaling methods. They are both good upgrades. But like all code, they come with bugs and exploits. The problem is that core has refused to fix any of the bugs and exploits of Segwit and Taproot. Mainly because they don't think spam is a thing. Murch (core dev) doesn't know what spam is. And Zhao (head dev) calls it "use cases we have today" instead of calling it spam. And she claims Satoshi didn't have the foresight to plan for those "new use cases we have today". That is false. File sharing was NEVER a supported use case of 123b06, until core 30 anyways You could post a file on 123b06 only by obfuscating it to make it look like a genuine 123b06 transaction. Even OP admits thus much. Thought the rest of his childish and ridiculous monster analogy is pure bullshit.

I'm sorry to inform you that OP is full of shit. You've been gaslighted. - Op_return is some ways is less harmful than other spam methods. But the spammers would lose the segwit and taproot discounts. So they are not likely to switch to taproot. The coretards told us for 4 years that "the fees are the filter" and they are suddenly ignoring their own bullshit claims when it no longer suits them. - Ordinals are not inevitable. Someone suggested an ordinal filter 2 years ago. Coretards invited a bunch of spammers to bitch about censorship. And they also changed a definition in their documentation. Than they rejected the filter by claiming it's too controversial and based on the new definition they just changed. - We have Taproot and Segwit mainly as scaling methods. They are both good upgrades. But like all code, they come with bugs and exploits. The problem is that core has refused to fix any of the bugs and exploits of Segwit and Taproot. Mainly because they don't think spam is a thing. Murch (core dev) doesn't know what spam is. And Zhao (head dev) calls it "use cases we have today" instead of calling it spam. And she claims Satoshi didn't have the foresight to plan for those "new use cases we have today". That is false. File sharing was NEVER a supported use case of 123b06, until core 30 anyways You could post a file on 123b06 only by obfuscating it to make it look like a genuine 123b06 transaction. Even OP admits thus much. Thought the rest of his childish and ridiculous monster analogy is pure bullshit.

I'm sorry to inform you that OP is full of shit. You've been gaslighted. - Op_return is some ways is less harmful than other spam methods. But the spammers would lose the segwit and taproot discounts. So they are not likely to switch to taproot. The coretards told us for 4 years that "the fees are the filter" and they are suddenly ignoring their own bullshit claims when it no longer suits them. - Ordinals are not inevitable. Someone suggested an ordinal filter 2 years ago. Coretards invited a bunch of spammers to bitch about censorship. And they also changed a definition in their documentation. Than they rejected the filter by claiming it's too controversial and based on the new definition they just changed. - We have Taproot and Segwit mainly as scaling methods. They are both good upgrades. But like all code, they come with bugs and exploits. The problem is that core has refused to fix any of the bugs and exploits of Segwit and Taproot. Mainly because they don't think spam is a thing. Murch (core dev) doesn't know what spam is. And Zhao (head dev) calls it "use cases we have today" instead of calling it spam. And she claims Satoshi didn't have the foresight to plan for those "new use cases we have today". That is false. File sharing was NEVER a supported use case of 123b06, until core 30 anyways You could post a file on 123b06 only by obfuscating it to make it look like a genuine 123b06 transaction. Even OP admits thus much. Thought the rest of his childish and ridiculous monster analogy is pure bullshit.