pull down to refresh
110 sats \ 0 replies \ @BITC0IN 12 Dec 2023 freebie \ parent \ on: Inscriptions: the cure is worse than the disease bitcoin
Analogies aside, that really depends on the goal of the action.
For me this is just not to be party to this kind of harmful activity in as much as can be controlled with my own node. I don't have delusions about this making an impact on anything else outside my nodes mempool/ram.
These attackers do not get an entirely free ride on my resources. And I'd argue, they shouldn't be given one by you or anyone else who views them as attackers. The majority of node runners feel the same way, and yet don't know their configuration options to achieve this perspective.
Your concern for the mempool is probably fair. There's a tragedy of the commons that can happen there. But I see that as low probability, medium impact. I would think stratum V2 adoption helps with this concern, but I'm not sure.
So too can the same tragedy of the commons happen with block space via illegal content, and to a lesser extent, bloat.
There are no good solutions here.
waiting it out is fair and hopeful. preparing for the worst case scenario is also prudent.
That means developing tools and options before they are needed.
I hope you understand.
This may also interest you https://www.reddit.com/r/bsv/comments/18dhglr/is_this_why_kurt_has_such_a_grudge_against_luke/kcs69jc/?context=10000
https://m.stacker.news/7741