path: root/83/fa3b4f098ac72f2c20db1a47bdf37b0154c73b

Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <morcos@gmail.com>) id 1Z5dpR-0007oP-S4
	for bitcoin-development@lists.sourceforge.net;
	Thu, 18 Jun 2015 17:42:17 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.174 as permitted sender)
	client-ip=209.85.212.174; envelope-from=morcos@gmail.com;
	helo=mail-wi0-f174.google.com; 
Received: from mail-wi0-f174.google.com ([209.85.212.174])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Z5dpQ-000176-E4
	for bitcoin-development@lists.sourceforge.net;
	Thu, 18 Jun 2015 17:42:17 +0000
Received: by wibdq8 with SMTP id dq8so721022wib.1
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 18 Jun 2015 10:42:10 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.81.194 with SMTP id c2mr30035679wiy.94.1434649330302;
	Thu, 18 Jun 2015 10:42:10 -0700 (PDT)
Received: by 10.180.168.34 with HTTP; Thu, 18 Jun 2015 10:42:10 -0700 (PDT)
In-Reply-To: <e6da277c39b0354cdf24361e20a1fce2@riseup.net>
References: <55828737.6000007@riseup.net>
	<CANEZrP3M7+BsZKLFZV-0A_fC7NmMGbTDxsx3ywru3dSW78ZskQ@mail.gmail.com>
	<20150618111407.GA6690@amethyst.visucore.com>
	<CAPg+sBj_go==m6-++sA53imYdz4OLH4bkyiuAyEM8YR8CaTd=w@mail.gmail.com>
	<CAJHLa0OKXaUD6MnN4N6RGbNwrXx43jBm9MiELQK6BRw1OL3HNA@mail.gmail.com>
	<0ede5c200ce70e4d92541dd91749b4ea@riseup.net>
	<CAJHLa0NiDamkrbW2TMoTLqMPhzw0LBboNp1+_atBGDYMa135uw@mail.gmail.com>
	<e6da277c39b0354cdf24361e20a1fce2@riseup.net>
Date: Thu, 18 Jun 2015 13:42:10 -0400
Message-ID: <CAPWm=eX5Oc4QXkp3H5thPBPzJ-t7JGzF5pVaP+eSd0=h52ku=A@mail.gmail.com>
From: Alex Morcos <morcos@gmail.com>
To: justusranvier@riseup.net
Content-Type: multipart/alternative; boundary=f46d0444028ab5c50e0518ce53db
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(morcos[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1Z5dpQ-000176-E4
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Concerns Regarding Threats by a Developer
 to Remove Commit Access from Other Developers
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 18 Jun 2015 17:42:17 -0000

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

Let me take a pass at explaining how I see this.

1) Code changes to Bitcoin Core that don't change consensus:  Wladimir is
the decider but he works under a process that is well understood by
developers on the project in which he takes under reasonable consideration
other technical opinions and prefers to have clear agreement among them.

2) Changes to the consensus rules: As others have said, this isn't anyone's
decision for anyone else.  It's up to each individual user as to what code
they run and what rules they enforce.  So then why is everyone so up in
arms about what Mike and Gavin are proposing if everyone is free to decide
for themselves?  I believe that each individual user should adhere to the
principle that there should be no changes to the consensus rules unless
there is near complete agreement among the entire community, users,
developers, businesses miners etc.  It is not necessary to define complete
agreement exactly because every individual person decides for themselves.
I believe that this is what gives Bitcoin, or really any money, its value
and what makes it work, that we all agree on exactly what it is.  So I
believe that it is misleading and bad for Bitcoin to tell users and
business that you can just choose without concern for everyone else which
code you'll run and we'll see which one wins out.  No.  You should run the
old consensus rules (on any codebase you want) until you believe that
pretty much everyone has consented to a change in the rules.  It is your
choice, but I think a lot of people that have spent time thinking about the
philosophy of consensus systems believe that when the users of the system
have this principle in mind, it's what will make the system work best.

3) Code changes to Core that do change consensus: I think that Wladimir,
all the other committers besides Gavin, and almost all of the other
developers on Core would defer to #2 above and wait for its outcome to be
clear before considering such a code change.

I'm sure my description of point 2 is not the most eloquent or clear, but
maybe someone else can try to elucidate this principle if they've grasped
what I'm trying to say.





On Thu, Jun 18, 2015 at 1:04 PM, <justusranvier@riseup.net> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On 2015-06-18 16:28, Jeff Garzik wrote:
> > This is an engineering list.  The quote precisely describes how the
> > bitcoin
> > consensus system functions.
> >
> > Users' choice is largely binary:  Follow the rules, or bitcoin software
> > ignores you.
>
>
> Software engineers should understand that they have a binary choice:
> produce the software that your customers want, or the world will ignore
> your software.
>
> There is *no inherent value* to Bitcoin's software rules. The only value
> that is exists is that produced by the individuals who voluntarily
> choose to run the software.
>
> Failing to account for all design requirements is bad engineering.
> Nobody cares about the design features of a bridge to nowhere.
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iQIcBAEBCgAGBQJVgvoDAAoJECpf2nDq2eYj0h4P/0YaTsS963qpb63zvB6WlIPS
> 2lhCJ9FtAd3II5Et+5c/cisfJ9YI2OnM0y8nQpyB9NEOeueN1L1sLFcayE5aHASd
> EgF7F81AhQD2iSIVwQNs2qAzrZNC2/Nx+nBzBDcrgZ6gRiPpQdsNLy2p0OuZdOgX
> yG4xl6tKADB2kNi6tVPtZqUC300uQHvggtm+pexYilT0ojEbeVHCoDV40MNDZC2h
> 1kcdTnGU2SHJJqeZN2vChJCOMfhmK4JwKgoz7JRXe/GHkUUJKriE6Kb7SVczii9e
> 9qfcosbnR3gjATMoHFYuJX/nsUx52Q1LM9eQgvE8Ml+6Mim5bj2KCJFh7YISxSq9
> FhDujfZFCRRQLPJCSkEUePxU/LS7lmoTZXYl3Zz1j9zbq4ncpRHpIFy9QX6iIqK6
> Dursnge9ELQwB+H6HoosWRzxOZyo+oiGj17OngJvZYcvzrc2wjHbpZfVqSkmZepU
> SfJZ64O7yjjXjITwhOc4XF2drzvhsjTsHH5BIwdbCn82SoCkJIwXraj7sxIundli
> LUJBPiAE0csdmsvW/2kkxLsd9JwTw9lJ9Pf8fiqH3itgrkPkO5mf10DPPnay1SNk
> Wnm1bAJ05WnKXSo0m0SzaFgZkdfFuhWR4fieSzhLpa+s/HHj18NZvJCmCBR6ic9G
> 0A+51wwSZnAdMIw7lwIb
> =r4Co
> -----END PGP SIGNATURE-----
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

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

<div dir=3D"ltr">Let me take a pass at explaining how I see this.<div><br><=
/div><div>1) Code changes to Bitcoin Core that don&#39;t change consensus: =
=C2=A0Wladimir is the decider but he works under a process that is well und=
erstood by developers on the project in which he takes under reasonable con=
sideration other technical opinions and prefers to have clear agreement amo=
ng them.</div><div><br></div><div>2) Changes to the consensus rules: As oth=
ers have said, this isn&#39;t anyone&#39;s decision for anyone else.=C2=A0 =
It&#39;s up to each individual user as to what code they run and what rules=
 they enforce.=C2=A0 So then why is everyone so up in arms about what Mike =
and Gavin are proposing if everyone is free to decide for themselves?=C2=A0=
 I believe that each individual user should adhere to the principle that th=
ere should be no changes to the consensus rules unless there is near comple=
te agreement among the entire community, users, developers, businesses mine=
rs etc.=C2=A0 It is not necessary to define complete agreement exactly beca=
use every individual person decides for themselves.=C2=A0 I believe that th=
is is what gives Bitcoin, or really any money, its value and what makes it =
work, that we all agree on exactly what it is.=C2=A0 So I believe that it i=
s misleading and bad for Bitcoin to tell users and business that you can ju=
st choose without concern for everyone else which code you&#39;ll run and w=
e&#39;ll see which one wins out.=C2=A0 No.=C2=A0 You should run the old con=
sensus rules (on any codebase you want) until you believe that pretty much =
everyone has consented to a change in the rules.=C2=A0 It is your choice, b=
ut I think a lot of people that have spent time thinking about the philosop=
hy of consensus systems believe that when the users of the system have this=
 principle in mind, it&#39;s what will make the system work best.</div><div=
><br></div><div>3) Code changes to Core that do change consensus: I think t=
hat Wladimir, all the other committers besides Gavin, and almost all of the=
 other developers on Core would defer to #2 above and wait for its outcome =
to be clear before considering such a code change.</div><div><br></div><div=
>I&#39;m sure my description of point 2 is not the most eloquent or clear, =
but maybe someone else can try to elucidate this principle if they&#39;ve g=
rasped what I&#39;m trying to say.</div><div><br></div><div><br></div><div>=
<br></div><div><br></div></div><div class=3D"gmail_extra"><br><div class=3D=
"gmail_quote">On Thu, Jun 18, 2015 at 1:04 PM,  <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:justusranvier@riseup.net" target=3D"_blank">justusranvier@rise=
up.net</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"><span class=
=3D"">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA512<br>
<br>
</span>On 2015-06-18 16:28, Jeff Garzik wrote:<br>
&gt; This is an engineering list.=C2=A0 The quote precisely describes how t=
he<br>
&gt; bitcoin<br>
&gt; consensus system functions.<br>
&gt;<br>
&gt; Users&#39; choice is largely binary:=C2=A0 Follow the rules, or bitcoi=
n software<br>
&gt; ignores you.<br>
<br>
<br>
Software engineers should understand that they have a binary choice:<br>
produce the software that your customers want, or the world will ignore<br>
your software.<br>
<br>
There is *no inherent value* to Bitcoin&#39;s software rules. The only valu=
e<br>
that is exists is that produced by the individuals who voluntarily<br>
choose to run the software.<br>
<br>
Failing to account for all design requirements is bad engineering.<br>
Nobody cares about the design features of a bridge to nowhere.<br>
<span class=3D""><br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v2<br>
<br>
</span>iQIcBAEBCgAGBQJVgvoDAAoJECpf2nDq2eYj0h4P/0YaTsS963qpb63zvB6WlIPS<br>
2lhCJ9FtAd3II5Et+5c/cisfJ9YI2OnM0y8nQpyB9NEOeueN1L1sLFcayE5aHASd<br>
EgF7F81AhQD2iSIVwQNs2qAzrZNC2/Nx+nBzBDcrgZ6gRiPpQdsNLy2p0OuZdOgX<br>
yG4xl6tKADB2kNi6tVPtZqUC300uQHvggtm+pexYilT0ojEbeVHCoDV40MNDZC2h<br>
1kcdTnGU2SHJJqeZN2vChJCOMfhmK4JwKgoz7JRXe/GHkUUJKriE6Kb7SVczii9e<br>
9qfcosbnR3gjATMoHFYuJX/nsUx52Q1LM9eQgvE8Ml+6Mim5bj2KCJFh7YISxSq9<br>
FhDujfZFCRRQLPJCSkEUePxU/LS7lmoTZXYl3Zz1j9zbq4ncpRHpIFy9QX6iIqK6<br>
Dursnge9ELQwB+H6HoosWRzxOZyo+oiGj17OngJvZYcvzrc2wjHbpZfVqSkmZepU<br>
SfJZ64O7yjjXjITwhOc4XF2drzvhsjTsHH5BIwdbCn82SoCkJIwXraj7sxIundli<br>
LUJBPiAE0csdmsvW/2kkxLsd9JwTw9lJ9Pf8fiqH3itgrkPkO5mf10DPPnay1SNk<br>
Wnm1bAJ05WnKXSo0m0SzaFgZkdfFuhWR4fieSzhLpa+s/HHj18NZvJCmCBR6ic9G<br>
0A+51wwSZnAdMIw7lwIb<br>
=3Dr4Co<br>
<div class=3D"HOEnZb"><div class=3D"h5">-----END PGP SIGNATURE-----<br>
<br>
<br>
---------------------------------------------------------------------------=
---<br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" rel=3D"noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/=
listinfo/bitcoin-development</a><br>
</div></div></blockquote></div><br></div>

--f46d0444028ab5c50e0518ce53db--