summaryrefslogtreecommitdiff
path: root/ba/c8c03761066903f85de00450426eaaad923ef6
blob: ba3d2647c7def70d85103d230b21601d8e4033fd (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
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
Return-Path: <elombrozo@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 7F5FEA04
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sun, 28 Jun 2015 05:33:11 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-pa0-f53.google.com (mail-pa0-f53.google.com
	[209.85.220.53])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 60764F2
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sun, 28 Jun 2015 05:33:10 +0000 (UTC)
Received: by pactm7 with SMTP id tm7so88323684pac.2
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 27 Jun 2015 22:33:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=subject:mime-version:content-type:from:in-reply-to:date:cc
	:message-id:references:to;
	bh=w0hMqgsaSe8TEhMbgCScn7t+Dpay9LnbLRO8DC4FgQA=;
	b=AzHZ/pENAzQJJJ3a9Sjx1IdmY2V069I+YbwUUVk2NPFfZ8k9BKy80bWYtQlxlE+HES
	/szUvoH6e4JDfN/B5QQWKarqxWoh7GQOqNEOjQsmV61nh0G065aRcD0M+JRgR5xE8t93
	ycp8J8tMgKQ9ds4B3ear49ba3SYIELweU6kRfbJ5Nxl+AVNC9yqfnPhOfT5b8Z8vfiA/
	GwgC/yrtWeeXRktVI3rjWjJ7OJdd/RBNbX/c1JRQzIZag5x4kf+o7ZgKSOpYSZ9cnOwU
	gBgyj2+4KZ1X5VXE2jZCr+4gIQ1koqF8NODaQinVsB0Kj7qAzdnxx26ob89pu6o9hoxT
	dQhg==
X-Received: by 10.66.190.228 with SMTP id gt4mr19391860pac.72.1435469590078;
	Sat, 27 Jun 2015 22:33:10 -0700 (PDT)
Received: from [192.168.1.102] (cpe-76-167-237-202.san.res.rr.com.
	[76.167.237.202]) by mx.google.com with ESMTPSA id
	wh6sm37996656pbc.96.2015.06.27.22.32.59
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Sat, 27 Jun 2015 22:33:08 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Content-Type: multipart/signed;
	boundary="Apple-Mail=_42796B73-7D6B-4457-95F7-FD48F3DFE8E1";
	protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b6
From: Eric Lombrozo <elombrozo@gmail.com>
In-Reply-To: <558F8634.90904@gmail.com>
Date: Sat, 27 Jun 2015 22:32:57 -0700
Message-Id: <38C2E2A1-EB6C-48EB-8FA1-7FAA97B3E911@gmail.com>
References: <1164261435450448@web14h.yandex.ru> <558F583C.1000500@gmail.com>
	<2A94BDF7-F265-4D36-B438-DC4F432E1C67@gmail.com>
	<558F8634.90904@gmail.com>
To: Patrick Strateman <patrick.strateman@gmail.com>
X-Mailer: Apple Mail (2.2098)
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM,
	RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Original Vision
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development 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: Sun, 28 Jun 2015 05:33:11 -0000


--Apple-Mail=_42796B73-7D6B-4457-95F7-FD48F3DFE8E1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Just to clarify, SPV is fundamentally busted as it currently exists. =
I=E2=80=99m talking about potential optimizations for future protocols.

- Eric Lombrozo

> On Jun 27, 2015, at 10:29 PM, Patrick Strateman =
<patrick.strateman@gmail.com> wrote:
>=20
> Fraud proofs need to be at least more efficient than full node =
validation.
>=20
> Currently they are not.
>=20
> On 06/27/2015 09:54 PM, Eric Lombrozo wrote:
>> Fraud proofs actually don=E2=80=99t need to be made super =
efficient=E2=80=A6but they do need to be secure, of course.
>>=20
>> The trick is aligning incentives. In order for fraud proofs to be =
widely available there needs to be a market for them - there must be a =
way to buy one (because producing one is not free). What makes such a =
scheme actually practical is that very few of these fraud proofs ever =
need to actually be executed - it=E2=80=99s a classical Nimzowischian =
case of the threat being much stronger than the execution.
>>=20
>> - Eric Lombrozo
>>=20
>>> On Jun 27, 2015, at 7:13 PM, Patrick Strateman =
<patrick.strateman@gmail.com> wrote:
>>>=20
>>>> Further, it appears clear that the original author intended
>>> organizations operating full network nodes would provide =
connectivity to
>>> light clients and these light clients would make up the majority of =
the
>>> user base.
>>>=20
>>> Satoshi also believed that fraud proofs would be widely available =
and
>>> practical.
>>>=20
>>> If fraud proofs were practical SPV client security would be much =
closer
>>> to full node security than it is today.
>>>=20
>>> Unfortunately no design for fraud proofs which is both efficient and
>>> secure has been proposed; much less implemented and deployed.
>>>=20
>>> In building a system as new and innovative as bitcoin certain things
>>> will be wrong.
>>>=20
>>> The perception that SPV clients could be made nearly as secure as =
full
>>> nodes is one example of something that was wrong.
>>>=20
>>> On 06/27/2015 05:14 PM, Santino Napolitano wrote:
>>>> There is much heated debate going on right now and I know it can be =
very stressful but I'd like to point out that it is really amazing how =
passionately so many feel about this once very small project. Let's not =
forget there is something really special going on here and we're all =
part of it.
>>>>=20
>>>> The current debate has little to do with block size or hard-forks, =
IMO. It's about the nature of Bitcoin and what it means to people and =
how it will grow. I would like to take a moment to share my =
interpretation of the original author's intent based on everything I =
could find and read from this person. This is not to say their original =
vision is paramount-- or even that I got it completely correct but I =
think it might do us some good to think about.
>>>>=20
>>>> It seems as though the incentive conceived of for running a full =
network node was that it would enable mining. The proceeds from mining =
(new coins and transaction fees) would be the reward and provide a =
reason to continue operating these nodes. If fees are ever to be a =
sufficient reward and still allow for a practical and useful system the =
size of the blocks must grow significantly as must the user base. I'm =
not sure that this is really contested but I haven't exhaustively =
reviewed everyone's opinion so please excuse me if I have marginalized =
you. If you do contest that I would be interested in hearing it.
>>>>=20
>>>> Further, it appears clear that the original author intended =
organizations operating full network nodes would provide connectivity to =
light clients and these light clients would make up the majority of the =
user base. This is completely consistent with current trends in Internet =
consumption, e.g. tablets and phones are becoming more preferred to even =
owning a traditional computer. Having the system be entirely =
decentralized and trustless for every client does not appear to me to be =
the original design goal. Yes, the whitepaper speaks of the design goal =
as not having a need for a trusted third party but it does not say that =
some amount of trust won't be preferred by a majority of users. In fact, =
in the SPV section it implies some amount of localized trust is perhaps =
a necessary trade-off and maybe businesses should still run their own =
full network node if they want the stronger completely trustless =
guarantee. The global decentralized consensus appears meant to make the =
network
>>> r
>>>> esilient to a single government or other adversary's ability to =
shut the network down. If you really want to trust no one it is your =
option at a cost and should be possible by design. The author further =
gives evidence that they believe Moore's observation would keep the idea =
of running a full network node a practical one at global scale for =
perpetuity. It does not appear as if they intended for every individual =
to run one at home nor in their pocket.
>>>>=20
>>>> If my interpretation seems incorrect please do point it out. I hope =
this hasn't been too off-topic and distracting. The original author's =
engineering ingenuity is what gave me any interest in this project so =
re-visiting their design and scaling intentions might be helpful for us =
to move forward-- together.
>>>>=20
>>>> _______________________________________________
>>>> bitcoin-dev mailing list
>>>> bitcoin-dev@lists.linuxfoundation.org
>>>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>>=20
>>> _______________________________________________
>>> bitcoin-dev mailing list
>>> bitcoin-dev@lists.linuxfoundation.org
>>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>=20
>=20
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev


--Apple-Mail=_42796B73-7D6B-4457-95F7-FD48F3DFE8E1
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJVj4cJAAoJEJNAI64YFENUqzgP/iw+BotTixnpxOmiYUNX+xOu
7VJC6UrSbD6X6hNyAOu3jrRFnsie9HHMfniBjBh1il/+IBN9BW5+Sk3RhEnGGADl
8fjbwCkDoGnaaWsDoQvBZUOyDnnc1PK/hfOALgv5xG7++wXccmSMBeT65Ui5vIC2
rX4PuqN6kzCEkQQKOKXLfWPahBuM8vJZR/XmNiGS3Vsl/iliNinOdgSGIo1k/Lni
rQYaXNP4ZZufA4nhV6UdsSvrn8umI4s6AuCBrDpeWc6aiJG5a30BLNbqO5r7NuXk
LnF/VP8FtBcbFcJyLUVAktpowg1/BXAwwHx6DDXVnmxT+iber+mKgPcSUIz+QxOJ
hacVgeZpIZL0uFLBRIAW1YBuszVhxyBuF4V6uuX09nl4/OhnPTz39bF+bM0f4XIb
dimLdDZ/6XAQPbcpbdNeDkV+t2z4VBtakPrvbHHLRVWZcr6GOz2MRcqgt38u2Ha8
svgPNvcJxulnhCycKHWXnHuqGKwebusgEpWBTfVjwXpYarxVcvdWZ9f9i98cl9WG
eaLkriGEhFlHXdeq0t8ZSQ8ezTC3KBeF4PADhXOPhmFe0vP2K6f6SL/LX/9uUd4Y
ngZ7UwnWpoap6vtb3uTgW4UmOmRVCbctCBQXZMm0QSrpUj11PESxUpVBl7Nw2VAT
lSD5/ojj57USRg3uPPrK
=kL6J
-----END PGP SIGNATURE-----

--Apple-Mail=_42796B73-7D6B-4457-95F7-FD48F3DFE8E1--