Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 43526A73 for ; Wed, 12 Jul 2017 06:26:28 +0000 (UTC) X-Greylist: delayed 00:08:53 by SQLgrey-1.7.6 Received: from mail.osc.co.cr (unknown [168.235.79.83]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id EF893A7 for ; Wed, 12 Jul 2017 06:26:27 +0000 (UTC) Received: from [192.168.2.3] (miner1 [71.94.45.245]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: danda) by mail.osc.co.cr (Postfix) with ESMTPSA id 254591F2D2 for ; Tue, 11 Jul 2017 23:17:33 -0700 (PDT) To: Bitcoin Protocol Discussion References: <0119661e-a11a-6d4b-c9ec-fd510bd4f144@gmail.com> <1c1d06a9-2e9f-5b2d-42b7-d908ada4b09e@gmail.com> <001b20f2-1f33-3484-8ad2-1420ae1a2df5@gmail.com> From: Dan Libby Message-ID: <03cf3326-ae84-96f9-5eee-158054341eff@osc.co.cr> Date: Tue, 11 Jul 2017 23:17:24 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00,RDNS_NONE autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Thu, 13 Jul 2017 00:54:33 +0000 Subject: [bitcoin-dev] how to disable segwit in my build? 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, 12 Jul 2017 06:26:28 -0000 Hi! Up to now, I have purposefully been running bitcoin releases prior to 0.13.1 as a way to avoid the (possible) segwit activation, at least until such time as I personally am comfortable with it. At this time, I would like to have some of the more recent features, but without the possibility that my node will activate segwit, until I choose to. As I understand it, there is not any user setting that can disable segwit from activating on my node. If there was, I would use it. Please correct me if wrong. I am here to ask what is the simplest code change (fewest LOC changed) I can make to 0.14.2+ code that would disable segwit from activating and keep my node acting just like a legacy node with regards to consensus rules, even if/when the rest of the network activates segwit. I think, more generally, the same question applies to most any Bip9 versionbits feature. I'm not looking for reasons NOT to do it, only HOW to do it without unwanted side-effects. My first untested idea is just to change the segwit nTimeout in chainparams.cpp to a date in the past. But I figured I should ask the experts first. :-) thanks. ps: full disclosure: I may be the only one who wants this, but if successful, I do plan to release my changes in case someone else wishes to run with status-quo consensus rules.