summaryrefslogtreecommitdiff
path: root/37/f365b1925a64205fa2b42509961fd895fd38cc
blob: a940aa2a086b549ab7993fd7fbe15f55c6568adf (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
Return-Path: <rodney.morris@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 00611B75
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 31 Mar 2017 21:23:04 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wr0-f178.google.com (mail-wr0-f178.google.com
	[209.85.128.178])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 1AE7E13C
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 31 Mar 2017 21:23:03 +0000 (UTC)
Received: by mail-wr0-f178.google.com with SMTP id w11so113835566wrc.3
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 31 Mar 2017 14:23:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:from:date:message-id:subject:to;
	bh=wTy9PE6OtMgIFwRw1FFbTHo/sGZ8VhjDksX0Z87k0Tw=;
	b=BUxrH5mzWb9CdSQAj6MCPbKUP12DruOrc3qbmZo8BqnnpqjAlNHyM79mlar+7UNgYv
	AIl47ImkRnu4WUO91H4MfUbBme8AighWeRbZfuSRjXT+VIpVCdE+BBp46zAfmc3c49Mi
	TobkvChAB9IZCdguw4y45cVaIVe5nh7K8ZoAc2axIgLeZM1F8kbPCFS0Cqo+I0/tSINC
	Q5T+GcM7EH1aZE1cpmb0IT8kV+8mtmdRMUr3HlWk7+OhBePpjPTiuELR7yOVkBXkAKT7
	7zvtvXvOnjbtsCQpqENoM2rKzcxml/0KQXsSNn10pbcrXh1Xl9nxABfgP+DdeaKw9LnR
	gaAQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
	bh=wTy9PE6OtMgIFwRw1FFbTHo/sGZ8VhjDksX0Z87k0Tw=;
	b=S2IwPeGHUz3nAefmIvPd68PnBKT03e7D9zwCZPzk0e2XsGhTwYQsAXqhEo1HLlmpEy
	fWpiwMbpUl9SWNEql3BijBFLQk6tMC8bjA6hVk4/+LfdJCNbFMUCRCuemj3c9ZebZ/Js
	a99i6J1XExD+o/O+jg3nJ2XDUlzBx8E310yvFd1skuwLw8N5I0EqnfGVILPULzAJ7Fws
	ic7HqfNPHwgDwZttFxw3b5jBg/9w+/6h9MX+S+fCrTXuq1U+YLIBrkmdi+W5FKBzvQCt
	iYKIEIRMh07dUgygFmg0HnaquDr0knXLHyfupeiHRVPGbMQJR2kQUWM3HjychUbb6vMS
	xcrQ==
X-Gm-Message-State: AFeK/H1GB2xqSddSYNoaeE1vfEpdHVsGiTm9ejHrLY0LQXf5fCa885JJAYAibGtRw8VNFheDkfyMCBMy+KkcOw==
X-Received: by 10.223.169.70 with SMTP id u64mr4469417wrc.187.1490995381601;
	Fri, 31 Mar 2017 14:23:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.80.173.234 with HTTP; Fri, 31 Mar 2017 14:23:01 -0700 (PDT)
Received: by 10.80.173.234 with HTTP; Fri, 31 Mar 2017 14:23:01 -0700 (PDT)
From: Rodney Morris <rodney.morris@gmail.com>
Date: Sat, 1 Apr 2017 08:23:01 +1100
Message-ID: <CABerxhFY8NoA6sSiz1oZ=01Di8n9+QR1xE6NNtxvm=Ov1bGhWQ@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary=f403045cf46e1515fd054c0d6af5
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
	RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Fri, 31 Mar 2017 21:24:51 +0000
Subject: Re: [bitcoin-dev] Hard fork proposal from last week's meeting
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: Fri, 31 Mar 2017 21:23:04 -0000

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

You guessed wrong. Multiple data centres are as much about redundancy and
resiliency, and latency.

As for the cost, data centre space, business grade communication lines, and
staff are orders of magnitude more expensive than the physical hardware
they support.

I'd like to call you out on your continuing reduction to absurdity and
slippery slope arguments. Just because we can't handle 4GB blocks today,
doesn't mean we shouldn't aim in that direction. Doesn't mean we shouldn't
be taking our first second and third baby steps in that direction.

If the obsession with every personal computer being able to run a fill node
continues then bitcoin will be consigned to the dustbin of history, a
footnote to the story of the global crypto currency that eventually took
over the world.

Thanks
Rodney


Date: Fri, 31 Mar 2017 12:14:42 -0400
From: David Vorick <david.vorick@gmail.com>
To: Jared Lee Richardson <jaredr26@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Hard fork proposal from last week's meeting
Message-ID:
        <CAFVRnyqSMVj2Ttc4_5vuk73Z5yRJdxeSodvkdjqsrHbgghcmUQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"


Then explain why PayPal has multiple datacenters. And why Visa has multiple
datacenters. And why the banking systems have multiple datacenters each.

I'm guessing it's because you need that much juice to run a global payment
system at the transaction volumes that they run at.



Unless you have professional experience working directly with transaction
processors handling tens of millions of financial transactions per day, I
think we can fully discount your assessment that it would be a rounding
error in the budget of a major exchange or Bitcoin processor to handle that
much load. And even if it was, it wouldn't matter because it's extremely
important to Bitcoin's security that it's everyday users are able to and
are actively running full nodes.

I'm not going to take the time to refute everything you've been saying but
I will say that most of your comments have demonstrated a similar level of
ignorance as the one above.

This whole thread has been absurdly low quality.

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

<div dir=3D"auto"><div dir=3D"auto">You guessed wrong. Multiple data centre=
s are as much about redundancy and resiliency, and latency.=C2=A0</div><div=
 dir=3D"auto"><br></div><div dir=3D"auto">As for the cost, data centre spac=
e, business grade communication lines, and staff are orders of magnitude mo=
re expensive than the physical hardware they support.=C2=A0</div><div dir=
=3D"auto"><br></div><div dir=3D"auto">I&#39;d like to call you out on your =
continuing reduction to absurdity and slippery slope arguments. Just becaus=
e we can&#39;t handle 4GB blocks today, doesn&#39;t mean we shouldn&#39;t a=
im in that direction. Doesn&#39;t mean we shouldn&#39;t be taking our first=
 second and third baby steps in that direction.=C2=A0</div><div dir=3D"auto=
"><br></div><div dir=3D"auto">If the obsession with every personal computer=
 being able to run a fill node continues then bitcoin will be consigned to =
the dustbin of history, a footnote to the story of the global crypto curren=
cy that eventually took over the world.=C2=A0</div><div dir=3D"auto"><br></=
div><div dir=3D"auto">Thanks=C2=A0</div><div dir=3D"auto">Rodney=C2=A0</div=
><div><br><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote=
 class=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><br>
Date: Fri, 31 Mar 2017 12:14:42 -0400<br>
From: David Vorick &lt;<a href=3D"mailto:david.vorick@gmail.com">david.vori=
ck@gmail.com</a>&gt;<br>
To: Jared Lee Richardson &lt;<a href=3D"mailto:jaredr26@gmail.com">jaredr26=
@gmail.com</a>&gt;<br>
Cc: Bitcoin Dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org=
">bitcoin-dev@lists.<wbr>linuxfoundation.org</a>&gt;<br>
Subject: Re: [bitcoin-dev] Hard fork proposal from last week&#39;s meeting<=
br>
Message-ID:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;<a href=3D"mailto:CAFVRnyqSMVj2Ttc4_5vuk73Z=
5yRJdxeSodvkdjqsrHbgghcmUQ@mail.gmail.com">CAFVRnyqSMVj2Ttc4_<wbr>5vuk73Z5y=
RJdxeSodvkdjqsrHbgghc<wbr>mUQ@mail.gmail.com</a>&gt;<br>
Content-Type: text/plain; charset=3D&quot;utf-8&quot;<br><br>
<br>
Then explain why PayPal has multiple datacenters. And why Visa has multiple=
<br>
datacenters. And why the banking systems have multiple datacenters each.<br=
>
<br>
I&#39;m guessing it&#39;s because you need that much juice to run a global =
payment<br>
system at the transaction volumes that they run at.<br>
<br><br><br>
Unless you have professional experience working directly with transaction<b=
r>
processors handling tens of millions of financial transactions per day, I<b=
r>
think we can fully discount your assessment that it would be a rounding<br>
error in the budget of a major exchange or Bitcoin processor to handle that=
<br>
much load. And even if it was, it wouldn&#39;t matter because it&#39;s extr=
emely<br>
important to Bitcoin&#39;s security that it&#39;s everyday users are able t=
o and<br>
are actively running full nodes.<br>
<br>
I&#39;m not going to take the time to refute everything you&#39;ve been say=
ing but<br>
I will say that most of your comments have demonstrated a similar level of<=
br>
ignorance as the one above.<br>
<br>
This whole thread has been absurdly low quality.<br><br><br>
</blockquote></div><br></div></div></div>

--f403045cf46e1515fd054c0d6af5--