Some Bitcoiners are living in this imaginary world where the government is more likely to put them in jail for relaying bytes they don't even decode, than money transmission that they actually parse and validate but don't KYC... What governments are you living under folks??
nostr:nevent1qvzqqqqqqypzpmx6gv5vpwujnj3gtfp8vt60lltr956cafyyrl9hgf9hzqf83urjqyg8wumn8ghj7mn0wd68ytnddakj7qgwwaehxw309ahx7uewd3hkctcqypvcx7emqe0y07fx5w6suzanrekfrz83pj2cujjdenc0cwwz76yakzq2h26
2025-09-10 11:13:27
from 1 relay(s)
Replies (5)
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.
This hypothetical weird arguments can only be considered in comparison to the risk of filters on mining decentralisation but even worse client centralization and development takeover ... It is not that Knots people are just happily living with their filters, they literally say either everyone runs Knots or we are screwed... Now that smells, that to me sounds like a takeover attempt through FUD... I don't trust that.
Why on earth would you use Bitcoin as a relay when you can use Mainline DHT? Or Bittorrent with trackers? If you are ok with the data once confirmed, then you have to realise the relaying doesn't do anything whatsoever that is attractive to spammers, they don't want to relay their Jpegs, they want them to be included in the chain ... And if Bitcoin was being used more even that would quickly become too expensive that they will go back to using hashes + IPFS or Bittorrent.
Again, your node relaying Jpegs is worthless and no one will care about it least of all the government... When they have much bigger fish to fry; the fact that you are relaying money transmission messages, possibly to the benefit of their enemies
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).
Everyone can (and should) run whatever client they want.
But when someone tells you what client you should run it's when it starts stinking.
🫂
