Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 43038C002C for ; Mon, 11 Apr 2022 13:05:34 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 2454D82FA2 for ; Mon, 11 Apr 2022 13:05:34 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TqTVhGNp9VkJ for ; Mon, 11 Apr 2022 13:05:33 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.8.0 Received: from azure.erisian.com.au (azure.erisian.com.au [172.104.61.193]) by smtp1.osuosl.org (Postfix) with ESMTPS id F036F82F9E for ; Mon, 11 Apr 2022 13:05:32 +0000 (UTC) Received: from aj@azure.erisian.com.au (helo=sapphire.erisian.com.au) by azure.erisian.com.au with esmtpsa (Exim 4.92 #3 (Debian)) id 1ndtjT-0007L8-9N; Mon, 11 Apr 2022 23:05:29 +1000 Received: by sapphire.erisian.com.au (sSMTP sendmail emulation); Mon, 11 Apr 2022 23:05:22 +1000 Date: Mon, 11 Apr 2022 23:05:22 +1000 From: Anthony Towns To: Jorge =?iso-8859-1?Q?Tim=F3n?= , Bitcoin Protocol Discussion Message-ID: <20220411130522.GA3633@erisian.com.au> References: <20220315154549.GA7580@erisian.com.au> <20220322234951.GB11179@erisian.com.au> <20220326014546.GA12225@erisian.com.au> <20220330042106.GA13161@erisian.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Score-int: -18 X-Spam-Bar: - Subject: Re: [bitcoin-dev] Speedy Trial X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2022 13:05:34 -0000 On Fri, Apr 08, 2022 at 11:58:48AM +0200, Jorge Timón via bitcoin-dev wrote: > On Wed, Mar 30, 2022 at 6:21 AM Anthony Towns wrote: > > > Let's discuss those too. Feel free to point out how bip8 fails at some > > > hypothetical cases speedy trial doesn't. > > Any case where a flawed proposal makes it through getting activation > > parameters set and released, but doesn't achieve supermajority hashpower > > support is made worse by bip8/lot=true in comparison to speedy trial > I disagree. Also, again, not the hypothetical case I want to discuss. You just said "Let's discuss those" and "Feel free to point out how bip8 fails at some hypothetical cases speedy trial doesn't", now you're saying it's not what you want to discuss? But the above does include your "evil soft fork" hypothetical (I mean, unless you think being evil isn't a flaw?). The evil soft fork gets proposed, and due to some failure in review, merged with activation parameters set (via either speedy trial or bip8), then: a) supermajority hashpower support is achieved quickly: - both speedy trial and bip8+lot=true activate the evil fork b) supermajority hashpower support is achieved slowly: - speedy trial does *not* activate the evil fork, as it times out quickly - bip8 *does* activate the fork c) supermajority hashpower support support is never achieved: - speedy trial does *not* activate the evil fork - bip8+lot=false does *not* activate the evil fork, but only after a long timeout - bip8+lot=true *does* activate the evil fork In case (a), they both do the same thing; in case (b) speedy trial is superior to bip8 no matter whether lot=true/false since it blocks the evil fork, and in case (c) speedy trial is better than lot=false because it's quicker, and much better than lot=true because lot=true activates the evil fork. > > > > 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 > > > "That guy's incoherent raving" > > > "I'm just disagreeing". > > > > Uh, you realise the above is an alternative hypothetical, and not talking > > about you? I would have thought "that guy" being "an enemy of bitcoin" > > made that obvious... I think you're mistaken; I don't think your emails > > are incoherent ravings. > Do you realize IT IS NOT the hypothetical case I wanted to discuss. Yes, that's what "alternative" means: a different one. > I'm sorry, but I'm tired of trying to explain. and quite, honestly, you > don't seem interested in listening to me and understanding me at all, but > only in "addressing my concerns". Obviously we understand different things > by "addressing concerns". > Perhaps it's the language barrier or something. My claim is that for *any* bad (evil, flawed, whatever) softfork, then attempting activation via bip8 is *never* superior to speedy trial, and in some cases is worse. If I'm missing something, you only need to work through a single example to demonstrate I'm wrong, which seems like it ought to be easy... But just saying "I disagree" and "I don't want to talk about that" isn't going to convince anyone. I really don't think the claim above should be surprising; bip8 is meant for activating good proposals, bad ones need to be stopped in review -- as "pushd" has said in this thread: "Flawed proposal making it through activation is a failure of review process", and Luke's said similar things as well. The point of bip8 isn't to make it easier to reject bad forks, it's to make it easier to ensure *good* forks don't get rejected. But that's not your hypothetical, and you don't want to talk about all the ways to stop an evil fork prior to an activation attempt... Cheers, aj