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 0FC1594B for ; Wed, 26 Apr 2017 18:34:05 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from zinan.dashjr.org (zinan.dashjr.org [192.3.11.21]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 439158C for ; Wed, 26 Apr 2017 18:34:03 +0000 (UTC) Received: from ishibashi.localnet (unknown [IPv6:2001:470:5:265:a45d:823b:2d27:961c]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id AD3F538ABAA2; Wed, 26 Apr 2017 18:33:58 +0000 (UTC) X-Hashcash: 1:25:170426:bitcoin-dev@lists.linuxfoundation.org::8JcTbNm04w3cRr5b:uG=g X-Hashcash: 1:25:170426:shaolinfry@protonmail.ch::lB/OEUdPzx+4AOAJ:fORp From: Luke Dashjr To: bitcoin-dev@lists.linuxfoundation.org, shaolinfry Date: Wed, 26 Apr 2017 18:33:56 +0000 User-Agent: KMail/1.13.7 (Linux/4.9.16-gentoo; KDE/4.14.29; x86_64; ; ) References: <_IaaOs7JIj5n_7RkafDqIPZgjZ_RqHLKjgpEfQeGJzapvyfkYJIRWjWE6oxpoVTnsr4O8_HSg10mpHCpxdlyQFboFlqnmhgNGSUzqdp-jNY=@protonmail.ch> In-Reply-To: <_IaaOs7JIj5n_7RkafDqIPZgjZ_RqHLKjgpEfQeGJzapvyfkYJIRWjWE6oxpoVTnsr4O8_HSg10mpHCpxdlyQFboFlqnmhgNGSUzqdp-jNY=@protonmail.ch> X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201704261833.57577.luke@dashjr.org> 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 Subject: Re: [bitcoin-dev] Draft BIP: Segwit deployment with versionbits and guaranteed lock-in 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, 26 Apr 2017 18:34:05 -0000 See Segwit v2 thread. Maybe we can collaborate on combining these. On Wednesday 26 April 2017 6:15:26 PM shaolinfry via bitcoin-dev wrote: > This is a draft BIP proposal to redeploy segwit using BIP-8, from the day > after the current BIP9 segwit times out. > > This BIP could be deployed long before Nov 15th 2016, for example in July > allowing wide deployment to begin soon. The timeout (and this > useractivation) could be set to roughly a year from then. However, > considering around 70% of nodes upgraded to witness capability within 5-6 > months, I personally think we could reduce the time, especially > considering how much people want segwit - but I understand the need for > more caution in Bitcoin. > > Preliminary dates are deploy within a couple months, startdate Nov 16th > 2017, BIP8 timeout July 4th 2018. > > 
> BIP: ?
> Layer: Consensus (soft fork)
> Title: Segwit deployment with versionbits and guaranteed lock-in
> Author: Shaolin Fry 
> Comments-Summary: No comments yet.
> Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-????
> Status: Draft
> Type: Standards Track
> Created: 2017-04-14
> License: BSD-3-Clause
> CC0-1.0
>
> > ==Abstract== > > This document specifies a user activated soft fork for BIP141, BIP143 and > BIP147 using versionbits with guaranteed lock-in. > > ==Motivation== > > Miners have been reluctant to signal the BIP9 segwit deployment despite a > large portion of the Bitcoin ecosystem who want the soft fork activated. > This BIP specifies a user activated soft fork (UASF) that deploys segwit > again using versionbits with guaranteed lock-in on timeout if the BIP is > not already locked-in or activated by the timeout. This ensures users have > sufficient time to prepare and no longer require a miner supermajority, > while still allowing for an earlier miner activated soft fork (MASF). > > ==Reference implementation== > > https://github.com/bitcoin/bitcoin/compare/master...shaolinfry:uasegwit-fla > gday > > ==Specification== > > This deployment will set service bit (1<<5) as NODE_UAWITNESS. > > ==Deployment== > > This BIP will be deployed by BIP8 with the name "uasegwit" and using bit 2. > > For Bitcoin mainnet, the BIP8 starttime will be midnight 16 November 2017 > UTC (Epoch timestamp 1510790400) and BIP8 timeout will be 4 July 2018 UTC > (Epoch timestamp 1530662400). > > For Bitcoin testnet, segwit is already activated so no deployment is > specified. > > ==Rationale== > > This BIP can be deployed well in advance of the BIP8 '''starttime''' so > that the '''timeout''' will be sufficiently far in the future to allow > Bitcoin users to uprgade in preparation. > > The '''starttime''' of this BIP is after the BIP9 "segwit" timeout to > remove compatibility issues with old nodes. > > ==References== > > https://github.com/bitcoin/bips/blob/master/bip-0008.mediawiki > > https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki > > https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki > > https://github.com/bitcoin/bips/blob/master/bip-0143.mediawiki > > https://github.com/bitcoin/bips/blob/master/bip-0147.mediawiki > > ==Copyright== > > This document is dual licensed as BSD 3-clause, and Creative Commons CC0 > 1.0 Universal.