summaryrefslogtreecommitdiff
path: root/8d/bab9c492b65ae91d8734478d170400ea04acf5
blob: 31dc3daf869266d7a8e2b581640882e9aa54bba6 (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
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 5B6A8267
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 30 Jul 2015 23:33:22 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-pd0-f178.google.com (mail-pd0-f178.google.com
	[209.85.192.178])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 2F9C9118
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 30 Jul 2015 23:33:21 +0000 (UTC)
Received: by pdjr16 with SMTP id r16so32518284pdj.3
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 30 Jul 2015 16:33:21 -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=CnAtZxJVgzywSe964Hv7dPXIjy2pLUe+HJtnhfPlB74=;
	b=i7FOTVoIJS60CJi7aYPwl9cRBB4c5ecfoFSsGIy04bWn6qbogL36Fg92VjK0VHbxPJ
	tIRITEibYEUdF4eKRDL6cl6JvDTkaT2Yklb68mhnyF2WSukGBNLMc9zwuNT0w2Ml+SAD
	69QIsfl9Dr6+3KQX6yYfG2TrrqiJsGCyglAXM5fiUcdD0ax0QACmpKDXUOt0lmwxgEHX
	/8f45LdD623fsWtkbeh65UzeRgZj55VOqyWHmK+VUbCrZvusvR7Ej+GGNzaHgr8e/yhx
	xTsbB+o2u21ofGZCqkeQLnLZLMFpAPJAnNDeidsrG4HAQjWwGn93GidwEVvnCtgWD8+q
	109g==
X-Received: by 10.70.49.73 with SMTP id s9mr110877665pdn.149.1438299200939;
	Thu, 30 Jul 2015 16:33:20 -0700 (PDT)
Received: from [192.168.1.107] (cpe-76-167-237-202.san.res.rr.com.
	[76.167.237.202]) by smtp.gmail.com with ESMTPSA id
	bd5sm4080043pdb.41.2015.07.30.16.33.18
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 30 Jul 2015 16:33:19 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Content-Type: multipart/signed;
	boundary="Apple-Mail=_2D22D003-1723-4421-8B70-7B66613502FF";
	protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5
From: Eric Lombrozo <elombrozo@gmail.com>
In-Reply-To: <F7601CF2-2B89-4D11-8B56-8FFF63A4063C@gmail.com>
Date: Thu, 30 Jul 2015 16:33:16 -0700
Message-Id: <25FD9AAD-99F5-4322-AF34-243F75AE82C4@gmail.com>
References: <1B7F00D3-41AE-44BF-818D-EC4EF279DC11@gmail.com>
	<CA+w+GKTfPXkVPaCC+3ZsQv=_DPMHoRwbigS40Testpyq4rZxsw@mail.gmail.com>
	<D25BD175-7099-4A6B-89BB-A35E94F555A9@gmail.com>
	<CA+w+GKTZV5sgXNU_xoBby1_X6eae=5_vhENmyKY0yxWHcBiU5g@mail.gmail.com>
	<37D282C2-EF9C-4B8B-91E8-7D613B381824@phauna.org>
	<CAAS2fgSaRqxi3X0J3F05nA-tyRRikY1whkpAOuGJJpFSAR017w@mail.gmail.com>
	<COL131-DS222F0D512C6A5B47BF62C2CD8C0@phx.gbl>
	<55B94FAD.7040205@mail.bihthai.net>
	<COL131-DS95F86B1D5B93CE1275911CD8C0@phx.gbl>
	<CALqxMTEUAtNxkYMQwA9g9xH_LiX98yYOooGjUho1T3fMY2J5jQ@mail.gmail.com>
	<CAEX2NSc6FXsDLEpRq7YOxQErpBxS7tW8Afk-T9VUyeb2qS2brQ@mail.gmail.com>
	<74767203-7F7A-4848-9923-DE1DE60A28B4@gmail.com>
	<F7601CF2-2B89-4D11-8B56-8FFF63A4063C@gmail.com>
To: Gavin <gavinandresen@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,HTML_MESSAGE,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 <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measure isn't
	temporary
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: Thu, 30 Jul 2015 23:33:22 -0000


--Apple-Mail=_2D22D003-1723-4421-8B70-7B66613502FF
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_8B9CA1DA-B755-4FFF-B1A6-C8C6F5AA1020"


--Apple-Mail=_8B9CA1DA-B755-4FFF-B1A6-C8C6F5AA1020
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On Jul 30, 2015, at 5:29 AM, Gavin <gavinandresen@gmail.com> wrote:
>=20
> it is hard to have a rational conversation about that when even simple =
questions like 'what is s reasonable cost to run a full node' are met =
with silence.

Some of the risks are pretty hard to quantify. But I think this misses =
the bigger point - it very well *might* be possible to safely raise this =
limit or even get rid of it by first fixing some serious issues with the =
protocol. But over six years into the project and these issues continue =
to be all-but-ignored by most of the community (including at least a few =
core developers). I don=E2=80=99t think it=E2=80=99s really a matter of =
whether we agree on whether it=E2=80=99s good to raise the block size =
limit, Gavin. I think it=E2=80=99s a matter of a difference in =
priorities.

- Eric

--Apple-Mail=_8B9CA1DA-B755-4FFF-B1A6-C8C6F5AA1020
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Jul 30, 2015, at 5:29 AM, Gavin &lt;<a =
href=3D"mailto:gavinandresen@gmail.com" =
class=3D"">gavinandresen@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">it is hard to have a rational conversation about =
that when even simple questions like 'what is s reasonable cost to run a =
full node' are met with silence.</span></div></blockquote></div><br =
class=3D""><div class=3D"">Some of the risks are pretty hard to =
quantify. But I think this misses the bigger point - it very well =
*might* be possible to safely raise this limit or even get rid of it by =
first fixing some serious issues with the protocol. But over six years =
into the project and these issues continue to be all-but-ignored by most =
of the community (including at least a few core developers). I don=E2=80=99=
t think it=E2=80=99s really a matter of whether we agree on whether =
it=E2=80=99s good to raise the block size limit, Gavin. I think it=E2=80=99=
s a matter of a difference in priorities.</div><div class=3D""><br =
class=3D""></div><div class=3D"">- Eric</div></body></html>=

--Apple-Mail=_8B9CA1DA-B755-4FFF-B1A6-C8C6F5AA1020--

--Apple-Mail=_2D22D003-1723-4421-8B70-7B66613502FF
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

iQIcBAEBCgAGBQJVurQ8AAoJEJNAI64YFENUY6wQALJhm8GrcmFPatCMVaOUBsZ/
5luQiNBNXnlwQ01PbZ9elZEYRh/YwcV9YeLNwcxnqsVfVaxpvklVHa9vTy9q6bwn
3HYOf6AcxYK5Of/MkGpxyH+WC3cVbaWVcbJjzZLZSK+5iebMy1RxAgAUK40y59dm
EFxmx4FziDQoPiGyukWi+FvcSAfrTKdrGGG+n3sisa51ZqHwNHwWlHquCOVKGqkK
Nq6HxEhgfTp0vtCxNBEB+kTuD38br9xui6SWx+Q7udvnHpgG9DIws0w0MY8TiL6z
8KBv7dIicQd5YhdW5aFke1nTjia/1aSj/qQr59od7Vd+yJB9uc57puZqldjiJMLL
+AONpNwwWFFgNgZ8Uz7uN0nZV0FtoXxv8RAYAP4b19jXwLDmesTf6EDve2XLfqUW
lbOaeFiLynFlBkikrKdTCD0qxwDb2xEjIjxe1HS9XL2Jn/7mqMrYKFqd8lAQlUxL
eaVI/Gym5nJ1kPGS9De7RA3zUEYsLZDXwhW5ZRWleAVD+zx520cCdlRjrQjUmqKC
wrIxHpUXVu1xE10mXVSzZ+/DUci2D/+dBw3/r9b4zgK1nDbKyQUdbodbm2tZYUx0
BBo1oyIZdzXTaUd856AdgvYkEUbIVLWZXXrOGLtFUUw+qL+PApU3mUXX+kPvo7gk
q5xk3Zyegt5Gh8jh6bo/
=RTv2
-----END PGP SIGNATURE-----

--Apple-Mail=_2D22D003-1723-4421-8B70-7B66613502FF--