summaryrefslogtreecommitdiff
path: root/5a/15c78d84530b794d651a275828a1c87f47a807
blob: a12a68f0369e87613d7f7c45d5a22e26ba5accb6 (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
Return-Path: <pete@petertodd.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 35ECA6C
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 28 Jan 2017 18:38:36 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from outmail148113.authsmtp.com (outmail148113.authsmtp.com
	[62.13.148.113])
	by smtp1.linuxfoundation.org (Postfix) with ESMTP id E5C3B192
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 28 Jan 2017 18:38:34 +0000 (UTC)
Received: from mail-c232.authsmtp.com (mail-c232.authsmtp.com [62.13.128.232])
	by punt21.authsmtp.com (8.14.2/8.14.2/) with ESMTP id v0SIMsaP028120;
	Sat, 28 Jan 2017 18:22:54 GMT
Received: from petertodd.org (ec2-52-5-185-120.compute-1.amazonaws.com
	[52.5.185.120]) (authenticated bits=0)
	by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id v0SIMqZ4045432
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Sat, 28 Jan 2017 18:22:53 GMT
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by petertodd.org (Postfix) with ESMTPSA id BE19C4009A;
	Sat, 28 Jan 2017 18:22:49 +0000 (UTC)
Date: Sat, 28 Jan 2017 18:22:25 +0000
In-Reply-To: <CAAy62_KUSNTjivwJT87K9f1c=k-6gdaLXEBJjcy2KK+uLSTWDA@mail.gmail.com>
References: <201701270107.01092.luke@dashjr.org>
	<CAAy62_+1OjF3V5g4wpOyW0KtNGodddJu_cxOfG-f+8LB7D=rPA@mail.gmail.com>
	<CAAy62_JuWMQ=HMmcw8GsQSDM8S+4LJeG1GHw1OdT+mQC3H-DOA@mail.gmail.com>
	<201701270414.18553.luke@dashjr.org>
	<CAAy62_LHtrx7k73kznMpPvheA--0T9YiHkjHArf2KK0Qt+ViUg@mail.gmail.com>
	<CAAy62_LeNi1djDmArX0RWW=rD0GJU9eSqCy0o4G9eg3Y7O+0Wg@mail.gmail.com>
	<CAMZUoKnxqxvPQehdWo1ZaHB-1-od4cHvJRDTmF5x7ty1CdLbUQ@mail.gmail.com>
	<CAMZUoK=eb3jgA7Rwt38tvZt0tYk7gRVPc_2=HUWg1L_vaD93uw@mail.gmail.com>
	<CAMZUoKmUH7ah7pnUgLHFtwYacw2=v3rJ0-csJ8thRy=REM92iw@mail.gmail.com>
	<CAB3F3DviHkQo9ndYphOgUvgSum9TTzX=AA_Acdf-9sZJ7TuHuQ@mail.gmail.com>
	<20170127212810.GA5856@nex>
	<CAAy62_KUSNTjivwJT87K9f1c=k-6gdaLXEBJjcy2KK+uLSTWDA@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: multipart/signed; boundary="----5BWSCRGOTHE0AH6FU8X8MC3D5QV2DE"; 
	protocol="application/pgp-signature"; micalg="pgp-sha512"
To: Andrew Johnson <andrew.johnson83@gmail.com>,
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
	Andrew Johnson via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>, 
	Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>,
	Christian Decker <decker.christian@gmail.com>
From: Peter Todd <pete@petertodd.org>
Message-ID: <20E4FCBB-E841-4F8C-9906-743E4A023259@petertodd.org>
X-Server-Quench: c8d29c03-e586-11e6-829f-00151795d556
X-AuthReport-Spam: If SPAM / abuse - report it at:
	http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
	aQdMdAoUElQaAgsB AmEbWlxeUl97XGA7 bghPaBtcak9QXgdq
	T0pMXVMcUgULeGFA bBoeVhx2dAcIeX92 YU8sDXgPXk0pdUVg
	F0tcE3AHZDJmdWgd WRZFdwNVdQJNdxoR b1V5GhFYa3VsNCMk
	FAgyOXU9MCtqYBhV WAwAZVIbW0oFGSQ/ AgoPGTwzEEFNbQQL NHQA
X-Authentic-SMTP: 61633532353630.1037:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 52.5.185.120/25
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
	anti-virus system.
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,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
Subject: Re: [bitcoin-dev] Three hardfork-related BIPs
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, 28 Jan 2017 18:38:36 -0000

------5BWSCRGOTHE0AH6FU8X8MC3D5QV2DE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
 charset=utf-8



On 27 January 2017 15:53:02 GMT-08:00, Andrew Johnson via bitcoin-dev <bit=
coin-dev@lists=2Elinuxfoundation=2Eorg> wrote:
>I'd also like to point out to Luke that Satoshi envisioned most full
>nodes
>running in data centers in the white paper, not every single user needs
>to
>run a full node to use bitcoin=2E  Not to present this as an argument
>from
>authority, but rather to remind us what the intention of the system was
>to
>be(p2p cash, not a settlement layer only afforded by the wealthiest and
>largest value transactions)=2E  That a lot of people want to continue to
>move
>in that direction shouldn't be a surprise=2E

Satoshi also thought that SPV clients would be able to use fraud proofs (c=
alled "alerts" in the white paper) to detect fraudulent behavior by miners,=
 and thus not have to completely trust those nodes in those datacenters=2E =
Unfortunately it turns out that fraud proofs are both a very difficult engi=
neering challenge to implement, and also offer much less security than once=
 thought=2E In fact, as per Satoshi's vision, SPV clients don't currently e=
xist; what's called SPV isn't what Satoshi was envisioning=2E

Of course, this wouldn't be the first time that aspects of Satoshi's visio=
n for Bitcoin turned out to be wrong: the white paper also refers to the "l=
ongest chain" rather than most-work chain, something that had to be fixed i=
n what's technically a hardfork after Bitcoin's initial release=2E
------5BWSCRGOTHE0AH6FU8X8MC3D5QV2DE
Content-Type: application/pgp-signature; name="signature.asc"
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----

iQE9BAABCgAnIBxQZXRlciBUb2RkIDxwZXRlQHBldGVydG9kZC5vcmc+BQJYjOFi
AAoJEGOZARBE6K+yz4MH/jwEkiU8OGBNm/EZYonY7qTIYA6ek4I8jjwvYbUS+79h
8ZNswhz3JWIbevup0RwFhwC948m3jLVH8QvsMr+QDQqo/Dvsq9uiiqg3l/6BnauV
4dZwjCyuIY3kWPO1LAkc1gJ7vRz8/SYwHaF0Oc4zZmQjGLLzfUj4YUCA+QgSetmd
Ch8B9Iqjc8xIIqN1ocyihDqM/TUJd4bjhQoqJtIIl90ivEmHsJPbVdOhOMZ/bsMd
ySR6JMvRaVKYDNKdnc246Z22bPh0XSkH4Qt8rxHZumeM0OvW9Mmd3YAGCQrCUyd+
aWvuZmMb8cc1E1m2SlWDmH4jDHDXdinIESYwcgyFEOE=
=x9DN
-----END PGP SIGNATURE-----

------5BWSCRGOTHE0AH6FU8X8MC3D5QV2DE--