A more accurate description:
Discussion
That post ignores transactions which are unidentifiable as spam, yet are spam, because they are hiding their data as (fake) transactions. Which bloats the UTXO set. So, no, not convincing at all. And I though Jimmy would know better.
Jimmy knows better. These transactions only happen at that scale because the filters in core that are meant to deter them to a larger degree are broken for years and Core refuses to fix them. There was a PR by Luke in 2023 that proposed a fix and they locked it citing “controversy”. At the same time the filter for op return is working, as proven by Unhosted Marcellus. And the current PR is trying to nuke it.
Interesting. So how do you filter a series of TXs using small OP_RETURN payloads, or payload as signatures, or payload as raw multisig, or payload as scripts, or payload as any of the new things that VC backed scammers can and will come up with, when forced?
Seriously interested. I just don't think there's a good answer.
datacarriersize=0
Works in Knots. Doesn’t work in Core even if you manually set it to 0.
This is a good rule of thumb, but there are instances where it’ll not work or you don’t want it set to zero. In the spam filtration tab in knots there is a lot of optionality. New filters can be added/deployed a faster and more frictionless than spammers finding vulnerabilities of figuring ways to bypass them.
That creates two problems:
- the ones creating the filters become a trusted and central authority and can subsequently be attacked by the state
- VCs can stay solvent longer than the ones who update the filters, can stay motivated
Maybe try knots before you cry about it. The options knots has allow for you to make up your own set of filters so its self sovereign, and it might be hard for some bitcoin normies to understand but self sovereignity is the opposite of central authority. For central authority you can look at the boys from core, muting unwanted comments, paying someone to post a PR, stuf like that.
Vented enough? Cool. First of all, I tried knots. It's running on one of my nodes, and I mined with OCEAN for as long as my miner worked. I am also sympathetic to Luke and to his views. And I am also peeved about the GitHub comment closing/re-opening for ACK etc.
However, that changes nothing about the fact that filters are - very unfortunately - ineffective in trying to reach an optimal behavior of the overall network. And crying about it doesn't help either.
Great response, thanks mate!