Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 2909EC000B for ; Thu, 17 Mar 2022 11:32:38 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 0475D40141 for ; Thu, 17 Mar 2022 11:32:38 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp2.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=jtimon-cc.20210112.gappssmtp.com Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vk31EUcaQAo8 for ; Thu, 17 Mar 2022 11:32:37 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-yw1-x1134.google.com (mail-yw1-x1134.google.com [IPv6:2607:f8b0:4864:20::1134]) by smtp2.osuosl.org (Postfix) with ESMTPS id 19F0440122 for ; Thu, 17 Mar 2022 11:32:36 +0000 (UTC) Received: by mail-yw1-x1134.google.com with SMTP id 00721157ae682-2e58e59d101so54147587b3.13 for ; Thu, 17 Mar 2022 04:32:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jtimon-cc.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=hrrghyP9q5CT+xguPNtUj1jkYYTtaD61O26JnATCGkE=; b=B95ZuKXj3UB57qpa2jePP8wldBd8U4W2uuitq3gKVj/nDW6byCsWh5aA4vWnfjhTqi FRokho38tgTZiv+NECSnGKSmNSMhiYpPjIBYhkjMxpjA1ozUQbxCOL18uEdHM01kYHHY eKL3pZ7VImKdm31/Nhnau9LQYovEyeHNDn06n1QB9GUTzT+4o7CuyCaVQMqzfb8pd2G/ oEUpYACS9jB0+wioNUx3xfd2OjT3gZLObADq9/3dnWiGie3w76MWZGBY71sm8XbqhiRa 8qy3/LqA99bPH7IxG8uRusjB82BRF1Ia9D8hJCznrv+rDn8zqZAmzPh/4xE/L23/q14a 9dqw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=hrrghyP9q5CT+xguPNtUj1jkYYTtaD61O26JnATCGkE=; b=lClHXLc/qDkZde8GBdKVvHJ82HuyVZoZHLbfWKNrKHBTA6PaOD9l//4E2HGSzuFzU/ qjOyrG8juPsC0zGrGH3tkLtFtokH5FHU2FpBClmoTC2FdPBLpo9Sh/PLxFO+cpV5W81U miC98H+FxS3wtizAGQj36nMUXQxlILYU9EB/djJf6bdWGe5Ypfwg9ipjmmq3TjR8u6+F 0BQLK8nG4Y4iTyre/M54qYbESu9NqNjLe8s/TB7Jr0fFPNROuF+fuXmcHqKqwfHVa8DQ LQcJAKXJvA6B/q4T0UsWiEFEIu9/YvHAHSTnGMWm35vh5QPt5AZ+OoQZ69gRhShy8AMF yKnw== X-Gm-Message-State: AOAM532LOMii+rrKudiqdj0DKBXOWS/aZsM68PI6fMpmom50y492XyGm suWKmfn1NpjoRI+RMeLd2HJ4IWhuPOiG2gXBprU9xA== X-Google-Smtp-Source: ABdhPJyya5uUaRo91cHhileHty7CLR+Dnw/3vwF6WBbFN6bCJvCUYokTDZ4BqvQv7X75OiJeyFkyZV42JHIcxUcleuQ= X-Received: by 2002:a81:4955:0:b0:2e5:9fb5:f3e9 with SMTP id w82-20020a814955000000b002e59fb5f3e9mr4858172ywa.441.1647516755898; Thu, 17 Mar 2022 04:32:35 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= Date: Thu, 17 Mar 2022 12:32:24 +0100 Message-ID: To: Billy Tetrud , Bitcoin Protocol Discussion Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Thu, 17 Mar 2022 11:52:12 +0000 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: Thu, 17 Mar 2022 11:32:38 -0000 On Fri, Mar 11, 2022 at 5:32 PM Billy Tetrud via bitcoin-dev wrote: > > I think involving users more in activation is a good avenue of thought fo= r improving how bitcoin does soft forks. I also think the idea you brought = up of some way for people to signal opposition is a good idea. I've suggest= ed a mechanism for signature-based user polling, I've also suggested a mech= anism where miners can actively signal for opposing a soft fork. It seems l= ike there should be some common ground between us in those ideas. Where it = seems we may perhaps unreconcilably disagree are that A. miners are users t= oo and generally have interests that are important and different than most = users, and giving them at least some mechanism to force discussion is appro= priate, and B. chain splits are no joke and should almost never be possible= accidentally and therefore we should make a significant effort to avoid th= em, which almost definitely means orderly coordination of miners. Any user polling system is going to be vulnerable to sybil attacks. > Do you have anything concrete you want to propose? An example mechanism? = Are you simply here advocating your support for BIP8+LOT=3Dtrue? Yes, I want BIP+LOT=3Dtrue (aka the original bip8). I also want users to be easily able to coordinate resistance to any given change, as I described in this thread and others and luke has done many times. I also generally oppose to speedy trial being used for any consensus rule change deployment. Imagine someone comes and proposes a block size increase through extension block softfork. Would you like them to use speedy trial or BIP8+LOT=3Dtrue for deployment?