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 DD45710ED for ; Mon, 4 Jan 2016 01:09:35 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from ozlabs.org (ozlabs.org [103.22.144.67]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 415DB10A for ; Mon, 4 Jan 2016 01:09:35 +0000 (UTC) Received: by ozlabs.org (Postfix, from userid 1011) id CDA0F14031B; Mon, 4 Jan 2016 12:09:32 +1100 (AEDT) From: Rusty Russell To: Luke Dashjr , Tomas In-Reply-To: <201512302347.17609.luke@dashjr.org> References: <1451493317.3215816.479282618.4F666D71@webmail.messagingengine.com> <201512301710.27154.luke@dashjr.org> <1451499779.3919416.479357794.2C21BFA1@webmail.messagingengine.com> <201512302347.17609.luke@dashjr.org> User-Agent: Notmuch/0.20.2 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Mon, 04 Jan 2016 10:01:26 +1030 Message-ID: <878u46s0j5.fsf@rustcorp.com.au> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED, RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Mon, 04 Jan 2016 02:10:00 +0000 Cc: bitcoin-dev@lists.linuxfoundation.org Subject: Re: [bitcoin-dev] [BIP Draft] Decentralized Improvement Proposals X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jan 2016 01:09:36 -0000 Luke Dashjr via bitcoin-dev writes: > On Wednesday, December 30, 2015 6:22:59 PM Tomas wrote: >> > The specification itself looks like an inefficient and bloaty reinvention >> > of version bits. >> >> The actual assignment of version bits isn't clear from the >> specification. Are you saying that any implementation that wants to >> propose a change is encouraged to pick a free version bit and use it? > > That should probably be clarified in the BIP, I agree. Perhaps it ought to be > assigned the same as BIP numbers themselves, by the BIP editor? (Although as a > limited resource, maybe that's not the best solution.) I thought about it, but it's subject to change. Frankly, the number of deployed forks is low enough that they can sort it out themselves. If we need something more robust, I'm happy to fill that role. Cheers, Rusty.