Thread
But the data is still on the blockchain on all the nodes. This is the part that I can’t wrap my head around. Every one says knots fixes this but the data is still there. Knots just chooses to pretend it’s not there? And I’m not saying that 30 is the route we should take. Im just confused.
Replies (1)
you can't force consensus changes or rewrite history no matter how you try.
limiting the ingress of garbage to the blocks is achievable, and has the extra benefit of favoring propagation of non-garbage transactions, and should be considered the prerogative of all users to be able to do this arbitrarily
i think even, to make a plugin that lets users write custom filter logic would be great, in fact, they could remove the baked in filter stuff altogether and replace it with that and i wouldn't have a complaint to make towards core. then you could rip out huge amounts of unnecessary, contentious code from the codebase of all bitcoin core based nodes and let users build and share their own custom filter logic. and it could include delaying the acceptance of new blocks with spam in them until the main chain has more blocks on top (so it would not share these blocks in IBD or propagate the blocks on the p2p network until after it's history and can't be rejected anymore).
