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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pete@petertodd.org>) id 1YqLS3-0008LF-Ao
for bitcoin-development@lists.sourceforge.net;
Thu, 07 May 2015 13:02:55 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of petertodd.org
designates 62.13.148.111 as permitted sender)
client-ip=62.13.148.111; envelope-from=pete@petertodd.org;
helo=outmail148111.authsmtp.net;
Received: from outmail148111.authsmtp.net ([62.13.148.111])
by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1YqLRz-0006Ax-KG for bitcoin-development@lists.sourceforge.net;
Thu, 07 May 2015 13:02:55 +0000
Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235])
by punt18.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t47D2iUZ005012;
Thu, 7 May 2015 14:02:44 +0100 (BST)
Received: from savin.petertodd.org (75-119-251-161.dsl.teksavvy.com
[75.119.251.161]) (authenticated bits=128)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t47D2eYv055117
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
Thu, 7 May 2015 14:02:43 +0100 (BST)
Date: Thu, 7 May 2015 09:02:40 -0400
From: Peter Todd <pete@petertodd.org>
To: Mike Hearn <mike@plan99.net>
Message-ID: <20150507130240.GA16681@savin.petertodd.org>
References: <554A91BE.6060105@bluematt.me>
<CANEZrP3wGWHdz+ut6pvke5TJJsc1rTFt8sn2KziX35oL5LAsyg@mail.gmail.com>
<CABm2gDpDvk2VsQ+mJ-BoeBKmvu9jBXNujZEFKuCStRNjFL6VOA@mail.gmail.com>
<CANEZrP2zAGCCBhNa4=9yw+A_Dn5o4SQXoPTE_qcJzZ1dFuF2tw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="r5Pyd7+fXNt84Ff3"
Content-Disposition: inline
In-Reply-To: <CANEZrP2zAGCCBhNa4=9yw+A_Dn5o4SQXoPTE_qcJzZ1dFuF2tw@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: 59d0f166-f4b9-11e4-b396-002590a15da7
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aQdMdgUUFVQNAgsB AmMbWlBeUF97XWc7 bA9PbARUfEhLXhtr
VklWR1pVCwQmRRgG chxLO19ycgBHeXk+ ZE9gXHAVWU0udRB8
REhJQ2lUbHphaTUb TRJbfgVJcANIexZF O1F6ACIKLwdSbGoL
NQ4vNDcwO3BTJTpY RgYVKF8UXXNDNDo7 TBNKJjQ9EAUkQS4p IhU9JzYB
X-Authentic-SMTP: 61633532353630.1023:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 75.119.251.161/587
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Score: -1.5 (-)
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 SPF_PASS SPF: sender matches SPF record
-0.0 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1YqLRz-0006Ax-KG
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Block Size Increase
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, 07 May 2015 13:02:55 -0000
--r5Pyd7+fXNt84Ff3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, May 07, 2015 at 01:29:44PM +0200, Mike Hearn wrote:
> What if Gavin popped up right now and said he disagreed with every current
> proposal, he disagreed with side chains too, and there would be no
> consensus on any of them until the block size limit was raised.
>=20
> Would you say, oh, OK, guess that's it then. There's no consensus so might
> as well scrap all those proposals, as they'll never happen anyway. Bye bye
> side chains whitepaper.
If Gavin had good points to make, he'd probably eventually change
everyone's mind.
But if he fails to do that at some point he'll just get ignored and for
all practical purposes won't be considered part of the consensus. Not
unlike how if someone suggested we power the blockchain via perpetual
motion machines they'd be ignored. Bitcoin is after all a decentralized
system so all power over the development process is held only by social
consent and respect.
At that point I'd suggest Gavin fork the project and go to the next
level of consensus gathering, the community at large; I'm noticing this
is exactly what you and Gavin are doing.
Speaking of, are you and Gavin still thinking about forking Bitcoin
Core? If so I wish you the best of luck.
Sent: Wednesday, July 23, 2014 at 2:42 PM
=46rom: "Mike Hearn" <mike@plan99.net>
To: "Satoshi Nakamoto" <satoshin@gmx.com>
Subject: Thinking about a fork
I don't expect a reply, just getting some thoughts off my chest. Writing th=
em down helps.
Forking Bitcoin-Qt/Core has been coming up more and more often lately in co=
nversation (up from zero not that long ago). Gavin even suggested me and hi=
m fork it ... I pointed out that maintainers don't normally fork their own =
software :)
The problem is that the current community of developers has largely lost in=
terest in supporting SPV wallets. Indeed any protocol change that might mea=
n any risk at all, for anyone, is now being bogged down in endless circular=
arguments that never end. The Bitcoin developers have effectively become t=
he new financial regulators: restricting options within their jurisdiction =
with "someone might do something risky" being used as the justification.
If alternative low-risk protocols were always easily available this would b=
e no problem, but often they require enormous coding and deployment effort =
or just don't exist at all. Yet, wallets must move forward. If we carry on =
as now there simply won't be any usable decentralised wallets left and Bitc=
oin will have become an energy-wasting backbone for a bunch of banks and pa=
yment processors. That's so far from your original vision, it's sad.
I know you won't return and that's wise, but sometimes I wish you'd left a =
clearer design manifesto before handing the reigns over to Gavin, who is in=
creasingly burned out due to all the arguments (as am I).
Source: https://www.reddit.com/r/Bitcoin/comments/2g9c0j/satoshi_email_leak/
--=20
'peter'[:-1]@petertodd.org
0000000000000000066f25b3196b51d30df5c1678fc206fdf55b65dd6e593b05
--r5Pyd7+fXNt84Ff3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
iQGrBAEBCACVBQJVS2JsXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAwNjZmMjViMzE5NmI1MWQzMGRmNWMxNjc4ZmMyMDZmZGY1
NWI2NWRkNmU1OTNiMDUvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkfsDygf/Q4RPO/mA9xWQi+DvJQWSgjVv
AU82enkAeUjXuJtH97KEBYq+CLeiT48D9JgoLdE0jn8SjXM4vGUSDv5hz22LrTI8
WJSoxJ4Poa21c77ry0e+2QI2YWKOTDe5adsUcgk4Wo+QWXVvIDlbZRd7l02k2CMR
kXqrygs+BLj/ytCDUfXmqJXQJhCGqhdrsXfyJzicYJfPaHSs4PvoE3dUHc5NEb4C
qMKIUVBqUQn4eRfX9pFLVhSicB23q6jqNXa+JI0/KRmLjW8JIuTV7kHWL09MQXje
QHoNy8i1NKS92mj8SkSz2VKKYPGX/lSbagql8TSyiFbb/Hyv/ZwqnApPeijePQ==
=yWzF
-----END PGP SIGNATURE-----
--r5Pyd7+fXNt84Ff3--
|
