pull down to refresh
100 sats \ 4 replies \ @Scoresby OP 16 Sep \ parent \ on: Nunchuk founder, Hugo, on filter debate: Believe in PoW bitcoin
Thanks for your answer.
I suppose we should assume that Core is compromised. I don't know what warning signs there would be, but I assume I probably wouldn't notice them (Any obvious attack seems like it would fail). So the safest route is to assume that they aren't on my side.
They could try to sneak something into the code unnoticed. But this seems unlikely; there are a lot of people watching the repository.
They could try to argue for consensus changes that are unsafe. Maybe try to push through a scripting change that is not fully understood and allows some sort of damaging functionality.
Whatever the case, my response is that I'm not running the latest version until I agree with the arguments/reasons behind it.
In the case of changing the datacarriersize defaults, I agree with the arguments.
reply
Good point. I haven't changed it.
Why haven't I changed it? In general, this question of spam and relaying it seems like a very minor issue to me. I haven't felt it was important enough to merit much action at all.
By the same token, when 30 is released I will likely not upgrade for a few months; but this is my practice with all releases -- I like to be a lagging updater.
But I have no doubt that I'll be running 30 eventually.
reply
reply
As is the case with most of the more inconsequential details of my node's configuration, I don't mind when updates change them.
reply