From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 0B0CAFAF for ; Wed, 14 Feb 2018 22:20:34 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-vk0-f50.google.com (mail-vk0-f50.google.com [209.85.213.50]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 7DD051C0 for ; Wed, 14 Feb 2018 22:20:33 +0000 (UTC) Received: by mail-vk0-f50.google.com with SMTP id o17so6555923vke.7 for ; Wed, 14 Feb 2018 14:20:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=9v/yo480Paz3AwgKI+KWSKYuNDF5t//txJpGhpFETzs=; b=RN1A5lnQDAbiie6YF4segE2uiVFzfAuLKIrlWDXKp5Mz+9ROEY5JmKNc0bodsK+tO8 6nR1UGNN6KsKf8s/hsEIJczGjAxckDT9KPUKJ9MqJBgaH84VRrs5BM5nS8zonXfVnoNZ b8ctjY+rxQTpS8q4dBmtbsuSMDy4OK/IH/fFdLsJLMJUZkLjdUSzD6KK8QQR2GejXyIW A9P/eutsPB9eQBKmhr2jNXmzJBFBe1in3sOr8vjozGYHjEEG381KjEF3OvDALbafWuvw a5oyHQ6UnWzOj6rPtkHcZkOGcyJnbTPRHLCy9wMB+ykI2SJNUNgROR/glAhRmfUGqwQm u0TA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=9v/yo480Paz3AwgKI+KWSKYuNDF5t//txJpGhpFETzs=; b=XTqpKmlOpENAUOCaCygPH5kIU+5zM6vZaVJzgsygZ+CUPodIZR+B+0Fg2kqmBSnbhr 14Qp5Xarj/wrk79hi/oUrolUy1xD4i6B2qtQtBEeDE3lFgtxuytWS5dw8HDI6JyvY+bX P0wbhway50sG+7wo26Y01KYLYjXJ0mcCQOF2CxIxzX0dULP4Jjo2EjmFUVP9zyy+KOLM 3MSDzV5sXrocsiQnPNbg8I5AfvPSE1BBqjVpVLSSr0lRahY3RhKggGFDz4gxCFe0Z2aq 0584r7n4Egvj9scVpGNPHdRJ7qVrD1+GkeXknVYc4XZOx5rGKeGYIfgXZFsDOW9p7nXK rfvQ== X-Gm-Message-State: APf1xPD/xP7Zx+rhOWKY0TTSO3r4ylnGaKj8rw0T5GWSMIyZgN0DwUOI MbXgFtxvZ8SGkEtZVUpI2muRnNLbSVDJiM8tt7w= X-Google-Smtp-Source: AH8x226Me+i6/AK2QvwBpNy3xuSy+U2askV7vWZjxTAG8h59kE2JEaUrieu5vVNY7oghpyMqodstkwgbMkBDfV4bpmk= X-Received: by 10.31.149.195 with SMTP id x186mr707400vkd.14.1518646832509; Wed, 14 Feb 2018 14:20:32 -0800 (PST) MIME-Version: 1.0 Sender: gmaxwell@gmail.com Received: by 10.103.136.69 with HTTP; Wed, 14 Feb 2018 14:20:31 -0800 (PST) In-Reply-To: <201802142211.44293.luke@dashjr.org> References: <201802142211.44293.luke@dashjr.org> From: Gregory Maxwell Date: Wed, 14 Feb 2018 22:20:31 +0000 X-Google-Sender-Auth: Cq585JG6YlxJ_aggG0lNEBrLgO4 Message-ID: To: Luke Dashjr , Bitcoin Protocol Discussion Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] Amend the BIP 123 process to include buried deployments X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Feb 2018 22:20:34 -0000 On Wed, Feb 14, 2018 at 10:11 PM, Luke Dashjr via bitcoin-dev wrote: > On Wednesday 14 February 2018 10:01:46 PM Marco Falke via bitcoin-dev wrote: >> BIP 123 suggests that BIPs in the consensus layer should be assigned a >> label "soft fork" or "hard fork". However, I think the differentiation >> into soft fork or hard fork should not be made for BIPs that document >> buried deployments. In contrast to soft forks and hard forks, buried >> deployments do not require community and miner coordination for a safe >> deployment. > > They also do not require software coordination. Therefore, why should there be > BIPs at all? Seems to me that we should instead add these documents to > https://github.com/bitcoin-core/docs In that sense, no but they help people understand the system (e.g. so they don't go look at implementations and confuse that the activations they expect are simply not there); and they aid other implementations in understanding what other people have already analyzed and concluded was safe. You could certainly get an analysis wrong for one of these things.