Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 9E16DC0001 for ; Wed, 3 Mar 2021 22:13:03 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 8069B842F1 for ; Wed, 3 Mar 2021 22:13:03 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: 0.598 X-Spam-Level: X-Spam-Status: No, score=0.598 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp1.osuosl.org (amavisd-new); dkim=pass (1024-bit key) header.d=lkcl.net 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 wZZ7nuZ5Didp for ; Wed, 3 Mar 2021 22:13:01 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.8.0 Received: from lkcl.net (lkcl.net [217.147.94.29]) by smtp1.osuosl.org (Postfix) with ESMTPS id 981DA842E1 for ; Wed, 3 Mar 2021 22:13:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lkcl.net; s=201607131; h=Content-Type:To:Subject:Message-ID:Date:From:In-Reply-To:References:MIME-Version; bh=EAX1tE2fXruxCWmPVMWgZjnTahH3HJg7JSXIE9NHyhc=; b=A4dhcH1T40h1smJ3RYfoSgrepPyWGIEd2gkPPREOz+QkHSDzMCWwrhlVjR9AAgbxVjauYECrpvrze15b963W452geAcm6zlcqPm8BE/s+YquGNBRNcO3JRAVIVjj93k01s7+go19bEIXWLnGtYV26k7PD0vDef0o5P7hortP5GQ=; Received: from mail-lf1-f48.google.com ([209.85.167.48]) by lkcl.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1lHZjh-0002zF-Qq for bitcoin-dev@lists.linuxfoundation.org; Wed, 03 Mar 2021 22:12:54 +0000 Received: by mail-lf1-f48.google.com with SMTP id e7so39771536lft.2 for ; Wed, 03 Mar 2021 14:12:38 -0800 (PST) X-Gm-Message-State: AOAM530KSZMkxTfle3G457D6cog1xoHR4OmV9h1ymZ/jtp0j/h7w7A7i alL5NoE7C1XXbr/1n5pazSCsF0ApCRq/7iyyAhM= X-Google-Smtp-Source: ABdhPJxM2kvT7RgfD4jNoF7UjBxZ7JVo6Z5KeCaLo6ik3gnmjWziDgS4qsVvbTjS2zE4Y6cayOxkK/RjpOkD78sWV18= X-Received: by 2002:ac2:5221:: with SMTP id i1mr504071lfl.160.1614809552892; Wed, 03 Mar 2021 14:12:32 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Luke Kenneth Casson Leighton Date: Wed, 3 Mar 2021 22:12:21 +0000 X-Gmail-Original-Message-ID: Message-ID: To: Bitcoin Protocol Discussion Content-Type: text/plain; charset="UTF-8" X-Mailman-Approved-At: Wed, 03 Mar 2021 22:59:34 +0000 Subject: Re: [bitcoin-dev] Making the case for flag day activation of taproot 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: Wed, 03 Mar 2021 22:13:03 -0000 would it help by first setting a regular period of e.g. 6 months when only at that time would consensus rules ever be changed? not, "6 months from now taproot will be introduced', a rule, "*any* consensus change regardless of what they are (including NO change) will *ONLY* be made at regular interval period X months". this stops dead efforts by bots to announce "consensus! rules! are changing!" because if it's not at the exact time-period it's clearly bullshit. l.