path: root/2a/ffe94ae0b8aa74391a4b75c027ffd0df4c95f9

Return-Path: <steven.pine@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 8FBCCB8A
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 15 Apr 2017 02:01:20 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wm0-f42.google.com (mail-wm0-f42.google.com [74.125.82.42])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 4CB8A8D
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 15 Apr 2017 02:01:19 +0000 (UTC)
Received: by mail-wm0-f42.google.com with SMTP id o81so3661666wmb.1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 14 Apr 2017 19:01:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to; 
	bh=IclPkQ3QKoG8tL8tPYnzLZcahbhxzD/z8uHtBUkj1LY=;
	b=gtkAj7omrco6ZbuJWdE7XY4BPNfRSlsGHLENxf6gSz7UYpFyQCNSy7QIpAw99gzsRk
	iCLrCpVT0Lll8V8R1Uf16AdOcDiftJMvfTwYvKS+G2P3P0R9zqS1Q3/uEzbWdQ/7mrUo
	2VeuYQQDpXjFQcqVG/t+jpGmQP3GXRWpjkZb5cIgw9JjLg68NvVs6hscagKiwJOXLJLg
	36U+OMMtMbIYsd26IE8dgXekmlaUXgcGFa28ehnC7vPowR7QrLDtrOPj1LmXwBi1Pyn6
	CYPocVdgXa5Qqkz+2lhJLG10CMbklzTxcImBoejoOZtNs8bdTPPlesmNGr1BhGiyhPBg
	34cA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to;
	bh=IclPkQ3QKoG8tL8tPYnzLZcahbhxzD/z8uHtBUkj1LY=;
	b=hvSgErJaKovYajr3ez930rDSg1B4k37jY7qhgMoUpaKBupkQ2fQ3mnHazvwwCV65Pc
	KLrC5d//ZuizFWS/UBeyADTIeZbgY3Ee2XwTNElLmNacZsCOQEtV7Ggq5VQmois8UnpH
	fMoUlA8lt71Nlk5M6Dd2ZpPd0JQbBrScSgG4ShnyM6Y3jsMAejMyjaw2dKl2hOYdKaY+
	bJAZIRRLycO7dzRSAObETQe5bSXkpJMlWOntL1aXYjpZpGeNDwoXGabwED8nT1XspSjY
	N6NGoIaq2AuidGX3EgZ5dUkA3wjZ7ezoOu+QugHk8KS3koTK8cqf95n8lm0K1goNwmT1
	ZCug==
X-Gm-Message-State: AN3rC/7l6gIJ9LoTVVqU07kvBBPQ/Y5MjPh3FCTbRYiv7dAUt/u2rB3C
	8tNUIGuH1BU014CEX7M5d6loEEv1+9qGQFQ=
X-Received: by 10.28.113.73 with SMTP id m70mr955119wmc.12.1492221677673; Fri,
	14 Apr 2017 19:01:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.37.130 with HTTP; Fri, 14 Apr 2017 19:01:17 -0700 (PDT)
In-Reply-To: <CAAS2fgRdSOu8N6L3+fBpnye+rM+W6+F=cePy=9oL4tJuCj=Jsw@mail.gmail.com>
References: <CAAS2fgRdSOu8N6L3+fBpnye+rM+W6+F=cePy=9oL4tJuCj=Jsw@mail.gmail.com>
From: Steven Pine <steven.pine@gmail.com>
Date: Fri, 14 Apr 2017 22:01:17 -0400
Message-ID: <CAAjy6kAi6L9=4tgtay3m3YUk8SLs3NxD0JXp78TWmJXVMNfASQ@mail.gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a114791f20621f3054d2aef2e
X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
	RCVD_IN_DNSWL_NONE, 
	RCVD_IN_SORBS_SPAM 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: Sat, 15 Apr 2017 02:12:21 +0000
Subject: Re: [bitcoin-dev] I do not support the BIP 148 UASF
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Apr 2017 02:01:20 -0000

--001a114791f20621f3054d2aef2e
Content-Type: text/plain; charset=UTF-8

> Segwit is a good improvement
and we should respect it by knowing that it's good enough to wait for,
and for however its activated to be done the best way we know how.

Regarding this last point I was under the impression that if Segwit did not
activate by November then core was going to move on, is that no longer the
case, does the core team plan on trying to activate Segwit in some other
way?

I am also curious, but has there been a softfork, hardfork, or other major
census change that was not rolled out and done by the core team? I only
mention this because BIP148, if it goes ahead (and is successful), would be
the first time a consensus change occurs outside of the core developers --
but again I am not an expert on the history of changes and could be wrong,
I only bring this up because core developers have in the past stressed they
are a part of the bitcoin ecosystem and not the drivers of it (at least
that is the ideal it seems).

My impression is that the community is ready for this and wants it, and if
that impression is correct it will go ahead. No one knows the future, and
simply assuming it's better to be slow and methodical isn't especially
convincing. Technology is in someways the history of failure, we like to
celebrate the seemingly sudden breakthroughs and successes but it's rare
that the original innovator retains a monopoly on their invention, more
often it becomes quickly refined and iterated upon as market forces take
hold to bring costs down and other external political issues
take precedence, all this is say that in ten years everyone could be
chuckling over the 3 year bitcoin scaling debate, or they could be using
litecoin, or ethereum or some other crypto coin, or something entirely
different, no one knows.

On Fri, Apr 14, 2017 at 3:56 AM, Gregory Maxwell via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> I do not support the BIP148 UASF for some of the same reasons that I
> do support segwit:  Bitcoin is valuable in part because it has high
> security and stability, segwit was carefully designed to support and
> amplify that engineering integrity that people can count on now and
> into the future.
>
> I do not feel the the approach proposed in BIP148 really measures up
> to the standard set by segwit itself, or the existing best practices
> in protocol development in this community.
>
> The primary flaw in BIP148 is that by forcing the activation of the
> existing (non-UASF segwit) nodes it almost guarantees at a minor level
> of disruption.
>
> Segwit was carefully engineered so that older unmodified miners could
> continue operating _completely_ without interruption after segwit
> activates.
>
> Older nodes will not include segwit spends, and so their blocks will
> not be invalid even if they do not have segwit support. They can
> upgrade to it on their own schedule. The only risk non-participating
> miners take after segwit activation is that if someone else mines an
> invalid block they would extend it, a risk many miners already
> frequently take with spy-mining.
>
> I do not think it is a horrible proposal: it is better engineered than
> many things that many altcoins do, but just not up to our normal
> standards. I respect the motivations of the authors of BIP 148.  If
> your goal is the fastest possible segwit activation then it is very
> useful to exploit the >80% of existing nodes that already support the
> original version of segwit.
>
> But the fastest support should not be our goal, as a community-- there
> is always some reckless altcoin or centralized system that can support
> something faster than we can-- trying to match that would only erode
> our distinguishing value in being well engineered and stable.
>
> "First do no harm." We should use the least disruptive mechanisms
> available, and the BIP148 proposal does not meet that test.  To hear
> some people-- non-developers on reddit and such-- a few even see the
> forced orphaning of 148 as a virtue, that it's punitive for
> misbehaving miners. I could not not disagree with that perspective any
> more strongly.
>
> Of course, I do not oppose the general concept of a UASF but
> _generally_ a soft-fork (of any kind) does not need to risk disruption
> of mining, just as segwit's activation does not.  UASF are the
> original kind of soft-fork and were the only kind of fork practiced by
> Satoshi. P2SH was activated based on a date, and all prior ones were
> based on times or heights.  We introduced miner based activation as
> part of a process of making Bitcoin more stable in the common case
> where the ecosystem is all in harmony.  It's kind of weird to see UASF
> portrayed as something new.
>
> It's important the users not be at the mercy of any one part of the
> ecosystem to the extent that we can avoid it-- be it developers,
> exchanges, chat forums, or mining hardware makers.  Ultimately the
> rules of Bitcoin work because they're enforced by the users
> collectively-- that is what makes Bitcoin Bitcoin, it's what makes it
> something people can count on: the rules aren't easy to just change.
>
> There have been some other UASF proposals that avoid the forced
> disruption-- by just defining a new witness bit and allowing
> non-upgraded-to-uasf miners and nodes to continue as non-upgraded, I
> think they are vastly superior. They would be slower to deploy, but I
> do not think that is a flaw.
>
> We should have patience. Bitcoin is a system that should last for all
> ages and power mankind for a long time-- ten years from now a couple
> years of dispute will seem like nothing. But the reputation we earn
> for stability and integrity, for being a system of money people can
> count on will mean everything.
>
> If these discussions come up, they'll come up in the form of reminding
> people that Bitcoin isn't easily changed at a whim, even when the
> whims are obviously good, and how that protects it from being managed
> like all the competing systems of money that the world used to use
> were managed. :)
>
> So have patience, don't take short cuts.  Segwit is a good improvement
> and we should respect it by knowing that it's good enough to wait for,
> and for however its activated to be done the best way we know how.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>



-- 
Steven Pine
(510) 517-7075

--001a114791f20621f3054d2aef2e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><span class=3D"gmail-im" style=3D"font-size:12.8px">&gt;<s=
pan style=3D"font-size:12.8px">=C2=A0Segwit is a good improvement</span><br=
 style=3D"font-size:12.8px"><span style=3D"font-size:12.8px">and we should =
respect it by knowing that it&#39;s good enough to wait for,</span><br styl=
e=3D"font-size:12.8px"><span style=3D"font-size:12.8px">and for however its=
 activated to be done the best way we know how.</span><div><span style=3D"f=
ont-size:12.8px"><br></span></div></span><div style=3D"font-size:12.8px"><s=
pan style=3D"font-size:12.8px">Regarding this last point I was under the im=
pression that if Segwit did not activate by November then core was going to=
 move on, is that no longer the case, does the core team plan on trying to=
=C2=A0activate=C2=A0Segwit in some other way?</span></div><div style=3D"fon=
t-size:12.8px"><span style=3D"font-size:12.8px"><br></span></div><div style=
=3D"font-size:12.8px"><span style=3D"font-size:12.8px">I am also curious, b=
ut has there been a softfork, hardfork, or other major census change that w=
as not rolled out and done by the core team? I only mention this because BI=
P148, if it goes ahead (and is successful), would be the first time a conse=
nsus change occurs outside of the core developers -- but again I am not an =
expert on the history of changes and could be wrong, I only bring this up b=
ecause core developers have in the past stressed they are a part of the bit=
coin ecosystem and not the drivers of it (at least that is the ideal it see=
ms).</span></div><div style=3D"font-size:12.8px"><span style=3D"font-size:1=
2.8px"><br></span></div><div style=3D"font-size:12.8px"><span style=3D"font=
-size:12.8px">My impression is that the community is ready for this and wan=
ts it, and if that impression is correct it will go ahead. No one knows the=
 future, and simply assuming it&#39;s better to be slow and methodical isn&=
#39;t especially convincing. Technology is in someways the history of failu=
re, we like to celebrate the seemingly sudden breakthroughs and successes b=
ut it&#39;s rare that the original innovator retains a monopoly on their in=
vention, more often it becomes quickly refined and=C2=A0iterated upon as ma=
rket forces take hold to bring costs down and other external political issu=
es take=C2=A0precedence, all this is say that in ten years everyone could b=
e chuckling over the 3 year bitcoin scaling debate, or they could be using =
litecoin, or=C2=A0ethereum=C2=A0or some other crypto coin, or something ent=
irely different, no one knows.</span></div></div><div class=3D"gmail_extra"=
><br><div class=3D"gmail_quote">On Fri, Apr 14, 2017 at 3:56 AM, Gregory Ma=
xwell via bitcoin-dev <span dir=3D"ltr">&lt;<a href=3D"mailto:bitcoin-dev@l=
ists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundati=
on.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I do not sup=
port the BIP148 UASF for some of the same reasons that I<br>
do support segwit:=C2=A0 Bitcoin is valuable in part because it has high<br=
>
security and stability, segwit was carefully designed to support and<br>
amplify that engineering integrity that people can count on now and<br>
into the future.<br>
<br>
I do not feel the the approach proposed in BIP148 really measures up<br>
to the standard set by segwit itself, or the existing best practices<br>
in protocol development in this community.<br>
<br>
The primary flaw in BIP148 is that by forcing the activation of the<br>
existing (non-UASF segwit) nodes it almost guarantees at a minor level<br>
of disruption.<br>
<br>
Segwit was carefully engineered so that older unmodified miners could<br>
continue operating _completely_ without interruption after segwit<br>
activates.<br>
<br>
Older nodes will not include segwit spends, and so their blocks will<br>
not be invalid even if they do not have segwit support. They can<br>
upgrade to it on their own schedule. The only risk non-participating<br>
miners take after segwit activation is that if someone else mines an<br>
invalid block they would extend it, a risk many miners already<br>
frequently take with spy-mining.<br>
<br>
I do not think it is a horrible proposal: it is better engineered than<br>
many things that many altcoins do, but just not up to our normal<br>
standards. I respect the motivations of the authors of BIP 148.=C2=A0 If<br=
>
your goal is the fastest possible segwit activation then it is very<br>
useful to exploit the &gt;80% of existing nodes that already support the<br=
>
original version of segwit.<br>
<br>
But the fastest support should not be our goal, as a community-- there<br>
is always some reckless altcoin or centralized system that can support<br>
something faster than we can-- trying to match that would only erode<br>
our distinguishing value in being well engineered and stable.<br>
<br>
&quot;First do no harm.&quot; We should use the least disruptive mechanisms=
<br>
available, and the BIP148 proposal does not meet that test.=C2=A0 To hear<b=
r>
some people-- non-developers on reddit and such-- a few even see the<br>
forced orphaning of 148 as a virtue, that it&#39;s punitive for<br>
misbehaving miners. I could not not disagree with that perspective any<br>
more strongly.<br>
<br>
Of course, I do not oppose the general concept of a UASF but<br>
_generally_ a soft-fork (of any kind) does not need to risk disruption<br>
of mining, just as segwit&#39;s activation does not.=C2=A0 UASF are the<br>
original kind of soft-fork and were the only kind of fork practiced by<br>
Satoshi. P2SH was activated based on a date, and all prior ones were<br>
based on times or heights.=C2=A0 We introduced miner based activation as<br=
>
part of a process of making Bitcoin more stable in the common case<br>
where the ecosystem is all in harmony.=C2=A0 It&#39;s kind of weird to see =
UASF<br>
portrayed as something new.<br>
<br>
It&#39;s important the users not be at the mercy of any one part of the<br>
ecosystem to the extent that we can avoid it-- be it developers,<br>
exchanges, chat forums, or mining hardware makers.=C2=A0 Ultimately the<br>
rules of Bitcoin work because they&#39;re enforced by the users<br>
collectively-- that is what makes Bitcoin Bitcoin, it&#39;s what makes it<b=
r>
something people can count on: the rules aren&#39;t easy to just change.<br=
>
<br>
There have been some other UASF proposals that avoid the forced<br>
disruption-- by just defining a new witness bit and allowing<br>
non-upgraded-to-uasf miners and nodes to continue as non-upgraded, I<br>
think they are vastly superior. They would be slower to deploy, but I<br>
do not think that is a flaw.<br>
<br>
We should have patience. Bitcoin is a system that should last for all<br>
ages and power mankind for a long time-- ten years from now a couple<br>
years of dispute will seem like nothing. But the reputation we earn<br>
for stability and integrity, for being a system of money people can<br>
count on will mean everything.<br>
<br>
If these discussions come up, they&#39;ll come up in the form of reminding<=
br>
people that Bitcoin isn&#39;t easily changed at a whim, even when the<br>
whims are obviously good, and how that protects it from being managed<br>
like all the competing systems of money that the world used to use<br>
were managed. :)<br>
<br>
So have patience, don&#39;t take short cuts.=C2=A0 Segwit is a good improve=
ment<br>
and we should respect it by knowing that it&#39;s good enough to wait for,<=
br>
and for however its activated to be done the best way we know how.<br>
______________________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
<wbr>linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wbr>org=
/mailman/listinfo/bitcoin-<wbr>dev</a><br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><d=
iv>Steven Pine<div>(510) 517-7075</div></div></div></div>
</div>

--001a114791f20621f3054d2aef2e--