My nuanced take:
I'm in favor of removing mempool filters from Bitcoins code base.
I'm also in favor of a fix for witness stuffing if possible.
Arbitrary data should go in OP return where it is meant to go. And people should pay the normal fee based on the weight of that transaction.
deprecate witness. push people to use schnorr signatures.
I could be wrong, but this is what your take sounds like.
"I'm in favor of removing ant-littering laws from the books. Trash should go on the sides of the road and people should pay the normal fine based on the weight of their garbage."
That's where you are wrong in your assumptions. Mempool filters are not laws. They do nothing that affects the chain.
Mempool filters are the laws of a person's node.
Yea. Your node. Not the blockchain.
You don't want arbitrary data, the solution is roll back and remove OP_RETUEN and Segwit.
Hard fork that will not succeed.
Even then there is probably a way.
I can only dream of getting rid of Segwit lol I know it’ll never happen tho…
Why get rid of SegWit? It’s necessary for Lightning.
Lightning can still work with regular Bitcoin transactions.
But...
There would be transaction malleability where txid can be changed before confirming
The work around would be using only confirmed transactions.
It's hard to tell if there are other problems because we have to back up and think about how that would actually work in practice.
Arbitrary data has been possible on chain since the beginning more or less. There's no need to remove segwit or OP_RETURN to to filter spam, since older versions of CORE and the present version of Knots already accomplish that.
yea but... they don't....
Are you sure about that?
Yes, here is a dust tx I made. Non standard. Broadcast via regular rpc submission at a standard fee from my node.
I'll make an OP_RETURN that's non standard too if you would like for me to prove it.
Also ALL versions of core currently have the default filters still. Including OP_RETURN limit at 80 bytes
There is no version of core that's released that has a higher limit.
That's good.
Have I not demonstrated that they don't prevent concensous transactions?
I'm saying your statement is a good thing. I've been under the impression that the newest version of CORE has OP_RETURN limit removed, or something along those lines. But I stand corrected. "Also ALL versions of core currently have the default filters still. Including OP_RETURN limit at 80 bytes
There is no version of core that's released that has a higher limit."
I'm saying my statement shows why filters don't work and are unnecessary.
proof: https://mempool.happytavern.co/tx/58ae7a318f19c580b14d3547d6c65d1a417bbe8980189d34c61b2d4161741dfb
They are laws for transactions held in the memory of your PC.
will removing filter HELP in some way?
No. Removing them, removes useless code from the code base.
OP Return is a lot more useful even tho no discount. Easier to parse. Should solve itself thru market forces? I could be wrong- combining removing OP Return limits while adding a witness limit would be even better. Like a practical compromise between Knots and Core.
Limits don't do anything but protect the user from making unintended transactions. Remove them all of it were up to me. Make the code base smaller, more maintainable and less opinionated.
Totally agree! Getting rid of mempool filters can help make things smoother. And yeah, OP_RETURN seems like the right spot for random data. Let’s keep Bitcoin efficient and fair! 💪🚀
