reply on: Bitcoin devs cheer block reconstruction stats, ignore security budget concerns \ stacker news ~bitcoin

pull down to refresh

0 sats \ 1 reply \ @028559d218 13h \ parent \ on: Bitcoin devs cheer block reconstruction stats, ignore security budget concerns bitcoin

Thanks for your comment. You don't need to tell me... I have written post after post about, to the best of my knowledge and ability, about why Knots doesn't make any sense.

I don't know what the 'run knots' crowd is going to do after v30 is released (and their nodes download and verify blocks) or after knots were to become a larger percentage of the network... and the same transactions make it into blocks.

Hard fork?

They seem to think that at 51% 'knots' something magical happens which doesn't make any sense.

What all the drama is about is people who literally have no clue what the fuck they are talking about forming an echo chamber. The Knots echo chamber is infinitely worse in terms of absolute ignorance than the Core echo chamber (though much less powerful, so I guess they're equally horrendous.)

I used to run different relay filters, op_return sizes etc as Umbrel makes it really easy to change but honestly it just feels so pointless. The 'run knots' people would be much better off using Bitcoin regularly and frequently than spinning up more nodes which... from what I can tell they never/rarely use. Talk is cheap.

0 sats \ 0 replies \ @optimism 13h

I think that maxuploadtarget is a much more useful setting if you're trying to run a node than any filter or otherwise will help, unless you're actually running a watchtower. In that case, you want to disable all filters and know everything, and peer with as a diverse set of other nodes, so that you see ALL, and you won't get rugged by an asshole LN channel partner or other L2 solution where you need to know everything in mempool you can know.