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 576E2BD1 for ; Sun, 20 Dec 2015 01:20:09 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from omr2.cc.vt.edu (outbound.smtp.vt.edu [198.82.183.121]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 2DBF92F for ; Sun, 20 Dec 2015 01:20:07 +0000 (UTC) Received: from mr4.cc.vt.edu (mr4.cc.ipv6.vt.edu [IPv6:2001:468:c80:2105:0:232:8670:19fe]) by omr2.cc.vt.edu (8.14.4/8.14.4) with ESMTP id tBK1K6kk025705 for ; Sat, 19 Dec 2015 20:20:06 -0500 Received: from mail-pf0-f177.google.com (mail-pf0-f177.google.com [209.85.192.177]) by mr4.cc.vt.edu (8.14.4/8.14.4) with ESMTP id tBK1K13c009046 for ; Sat, 19 Dec 2015 20:20:06 -0500 Received: by mail-pf0-f177.google.com with SMTP id o64so68898171pfb.3 for ; Sat, 19 Dec 2015 17:20:06 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=k8vtTd+iecFLNFGzrrhTmzFz/5S2h3Q7Xrk3xeSmzfo=; b=aoidHy1R1HXNcK55OxgzNsBkyd5rG6uoZp9OWkrhXKqeSgFrNF7b9N0VkktHOjJI1T 5tDe7HNSc2KBOqarTZa0Thsnnsrt3qq0dlFSJFuM1N5XIy/TaZLNI0TFDLg8L/8mitBP YIm3N2Au6ry5I8vO1hDCgoOyg+IMtOIn/rE6pPVr5/E7g1G4U1HLJqOHxMUZJ9RfE/w8 qHXXkojeCwFfOLyYPDTIqnO8bod7X2oYgtN8cEMjFLq8jZXTXojvKsQGlgkReopSt8ef fWG1HlwcpgfgD3UtMrSgm4uoEXmC7WsrLwFMP85tTGFL42pl3Fei5xkf/XhlUeP7mj1s crZA== X-Gm-Message-State: ALoCoQnRUCCjKVJjoCq+E44lmxkBud8iR5MkcCvxgilq5XucT5/734vs1+BqFDjhuxMi7OU0G7+H5z8itxPF4O4QPr+lKOhdpq/ry1+LfSMwh5MtGfwwhl32MJAztCMP/zejiQ1SvcedTY2rbeNtkxphzZiHu7QRIc6TFFw6Wyuv8ptQU1xOD6HOzUW6R9gcD0lsUuJHTbeLweymALhNnxLKrzXWRX9MqsmK5OSGVGerDetjGLteugg= X-Received: by 10.98.11.203 with SMTP id 72mr16833223pfl.64.1450574401001; Sat, 19 Dec 2015 17:20:01 -0800 (PST) X-Received: by 10.98.11.203 with SMTP id 72mr16833210pfl.64.1450574400849; Sat, 19 Dec 2015 17:20:00 -0800 (PST) Received: from [192.168.1.230] (c-24-22-36-12.hsd1.or.comcast.net. [24.22.36.12]) by smtp.googlemail.com with ESMTPSA id v68sm26054782pfa.1.2015.12.19.17.19.59 for (version=TLSv1/SSLv3 cipher=OTHER); Sat, 19 Dec 2015 17:20:00 -0800 (PST) To: bitcoin-dev@lists.linuxfoundation.org References: From: Douglas Roark X-Enigmail-Draft-Status: N1210 Message-ID: <5676023F.1050509@vt.edu> Date: Sat, 19 Dec 2015 17:19:59 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED, T_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] Segregated witness softfork with moderate adoption has very small block size effect 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: Sun, 20 Dec 2015 01:20:09 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 2015/12/19 08:49, jl2012 via bitcoin-dev wrote: > P2SH has been introduced for 3.5 years and only about 10% of > bitcoin is stored this way (I can't find proportion of existing > P2SH address). A 1-year adoption rate of 40% for segwit is clearly > over-optimistic unless the tx fee becomes really high. I don't think one can necessarily conflate P2SH and SegWit uptake. In the case of P2SH, there's the "if it ain't broke, don't fix it" problem. P2PKH works just fine for an awful lot of Bitcoin users. Why should they switch over to P2SH? In the absence of a compelling reason, they'll probably stick to a proven solution. (You can see that line of thinking anywhere.) Even Armory, which values security and whiz-bang features over usability, offers P2SH but keeps it off by default. Meanwhile, SegWit fixes multiple problems, or at least fixes some while also sticking a bit of gum on others. True, it'll rely on wallet uptake. I just think wallet developers will see the value in it. The big question, of course, is when they'll enable it by default, which is the only way SegWit will gain serious traction. My personal, semi-educated guess is that you'll see 3-6 months of wallet integration and testnet tweaking, then another 3-6 months of mainnet availability if explicitly enabled by the user, and finally the switch being thrown for all wallet users. I'm hoping for the aggressive timeframes. I'm expecting the conservative ones. Is 40% optimistic? Maybe, and I'd personally like to see it enabled in concert with a minimal block size increase. I don't think 40% within a year of deployment is out of the realm of possibility, though. - -- - --- Douglas Roark Cryptocurrency, network security, travel, and art. https://onename.com/droark joroark@vt.edu PGP key ID: 26623924 -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWdgI/AAoJEEOBHRomYjkkZwsP/iZT+qa/Yp2xIE6ConcTrbbx IOmz6h4O+ro/Egx/6XrukBSRybn8gsjize279WQWjR0h7O3KS4YAGuR/TKx6IrOw cz7lZpwC08ZcZb83fUqEqz4q/Rbgp4cPU8WU1niLCYg2OCGqtTEhSSRatmO1ULXp 6KJrBCaoVBzaoqFXx6nXiJF/K1dKZsb/IuFFJZisXEmoDkvTunE82sjHZ+JgmHk9 jhhlk+JU43C7lXXkk+3KPbD+z3dMZNDYrIopaWOUXfk6yXIp8cy7MUK/z58PCm8C V/pTk0edkMIRxu6ybJLKNNZHqhSQipyEMfG/CojVb6Qtt8zC0RIEUsYj5uDk9RQL ITxql9RtPHQPx+uoxoCr7Zitx0448YFNpQs6S5/g81vDt7ilh5k5PgnILkMvuA7Y F6abFvsP/ahmAkisiyDzwMmcM+xzxvJkaY9aDvKy4NNiFw8kUxkAJ2VlMeQvwVTK 2ePzyrFTOGFJRk/a1uTr0aUOxpCdI8rB1O6jcrhmLl2ENRMjN1I3Ksl79Q6h3P+F zj3hR9CyuXrzoPxAISYF58ot32fil9nEnLcchu2mdWArYKBY2IDWVv7JiK8RCJ8b 2XymxccKsXIUHTrYJfrHg+AeRHkVuV8emyUp95A/8kb8meWbLbmpxOrt6JLEE4k9 qsl9Zkg/0IsCr+JzE6Ko =696M -----END PGP SIGNATURE-----