On Sat, Mar 26, 2022, 01:45 Anthony Towns wrote: > On Thu, Mar 24, 2022 at 07:30:09PM +0100, Jorge Timón via bitcoin-dev > wrote: > > Sorry, I won't answer to everything, because it's clear you're not > listening. > > I'm not agreeing with you; that's different to not listening to you. > You're disagreeing with thw premises of the example. That's not disagreeing, that's refusing to understand the example. > > In the HYPOTHETICAL CASE that there's an evil for, the fork being evil > > is a PREMISE of that hypothetical case, a GIVEN. > > Do you really find people more inclined to start agreeing with you when > you begin yelling at them? When other people start shouting at you, > do you feel like it's a discussion that you're engaged in? > I just wanted to make sure you catched the PREMISE word. > > Your claim that "if it's evil, good people would oppose it" is a NON > > SEQUITUR, "good people" aren't necessarily perfect and all knowing. > > good people can make mistakes, they can be fooled too. > > In the hypothetical case that THERE'S AN EVIL FORK, if "good people" > > don't complain, it is because they didn't realize that the given fork > > was evil. Because in our hypothetical example THE EVIL FORK IS EVIL BY > > DEFINITION, THAT'S THE HYPOTHETICAL CASE I WANT TO DISCUSS, not the > > hypothetical case where there's a fork some people think it's evil but > > it's not really evil. > > The problem with that approach is that any solution we come up with > doesn't only have to deal with the hypotheticals you want to discuss > Sure, but if it doesn't deal with this hypothetical, one canbot pretending it does by explaing how it does in a different hypothetical. In particular, any approach that allows you to block an evil fork, > even when everyone else doesn't agree that it's evil, would also allow > an enemy of bitcoin to block a good fork, that everyone else correctly > recognises is good. A solution that works for an implausible hypothetical > and breaks when a single attacker decides to take advantage of it is > not a good design. > Let's discuss those too. Feel free to point out how bip8 fails at some hypothetical cases speedy trial doesn't. And I did already address what to do in exactly that scenario: > > > > But hey what about the worst case: what if everyone else in bitcoin > > > is evil and supports doing evil things. And maybe that's not even > > > implausible: maybe it's not an "evil" thing per se, perhaps [...] > > > > > > In that scenario, I think a hard fork is the best choice: split out a > new > > > coin that will survive the upcoming crash, adjust the mining/difficulty > > > algorithm so it works from day one, and set it up so that you can > > > maintain it along with the people who support your vision, rather than > > > having to constantly deal with well-meaning attacks from "bitcoiners" > > > who don't see the risks and have lost the plot. > > > > > > Basically: do what Satoshi did and create a better system, and let > > > everyone else join you as the problems with the old one eventually > become > > > unavoidably obvious. > > > Once you understand what hypothetical case I'm talking about, maybe > > you can understand the rest of my reasoning. > > As I understand it, your hypothetical is: > > 0) someone has come up with a bad idea > 1) most of bitcoin is enthusiastically behind the idea > 2) you are essentially alone in discovering that it's a bad idea > 3) almost everyone remains enthusiastic, despite your explanations that > it's a bad idea > 4) nevertheless, you and your colleagues who are aware the idea is bad > should have the power to stop the bad idea > 5) bip8 gives you the power to stop the bad idea but speedy trial does not > Again given (0), I think (1) and (2) are already not very likely, and (3) > is simply not plausible. But in the event that it does somehow occur, > I disagree with (4) for the reasons I describe above; namely, that any > mechanism that did allow that would be unable to distinguish between the > "bad idea" case and something along the lines of > Ok, yeah, the bitcoin developers currently paying attention to the mailibg list being fooled or making a review mistake is completely unfeasible. They're all way to humble for that, obviously...sigh. 0') someone has come up with a good idea (yay!) > 1') most of bitcoin is enthusiastically behind the idea > 2') an enemy of bitcoin is essentially alone in trying to stop it > 3') almost everyone remains enthusiastic, despite that guy's incoherent > raving > 4') nevertheless, the enemies of bitcoin should have the power to stop > the good idea > > And, as I said in the previous mail, I think (5) is false, independently > of any of the other conditions. > "That guy's incoherent raving" "I'm just disagreeing". Never mind, anthony. Ypu absolutely understood what I'm saying. It's just that I'm also incoherent to you, it seems. But, hey, again, no contradiction here, I guess. > But if you don't understand the PREMISES of my example, > > You can come up with hypothetical premises that invalidate bitcoin, > let alone some activation method. For example, imagine if the Federal > Reserve Board are full of geniuses and know exactly when to keep issuance > predictable and when to juice the economy? Having flexibility gives more > options than hardcoding "21M" somewhere, so clearly the USD's approach > is the way to go, and everything is just a matter of appointing the > right people to the board, not all this decentralised stuff. > > The right answer is to reject bad premises, not to argue hypotheticals > that have zero relationship to reality > Ok, stop arguing a hypothetical you don't want to arhue about. But you can't say both "I don't want to consider that hypothetical" and "we considered all hypotheticals" at the same time. I mean, you can, you only can't if you don't want to contradict yourself. I'll have to wait for someone who actually can both understand the hypothetical and ve willing to discuss it. I think you didn't understand it, but either way: thank you for admitting you don't want to discuss it. Let's stop wasting each other's time then. Cheers, > aj > >