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
|
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 B8B46307
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 23 Jul 2015 01:53:39 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-pa0-f50.google.com (mail-pa0-f50.google.com
[209.85.220.50])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 55206F7
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 23 Jul 2015 01:53:39 +0000 (UTC)
Received: by pacan13 with SMTP id an13so149467919pac.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 22 Jul 2015 18:53:39 -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=5fE61RyvR60vgenol+wCqthHZhhPYbnTB0mT0Qzv3SU=;
b=oQUk3qA6rftU4xpfY120QT/EMvX5P38NiHD4bP0u+x+Ik2kfMAFvKolHJLjx8/opRF
UfPHVJYComjBsMBh3LgmR2k+iTKxiI8s3Vp+eHm0lbhLpH+FiDWgZ1OIDFg5qEJ95VGq
FsgraFJvYTiBjilXYGZ/vUeicp+rqLlxIJ45sDxYxzpgEDwmwJDG5i7kfcuoTYgbpdiN
YBelg/vC1mhHZzOSU1qsyIIlVlbPmrgIAcN42noj/S0JcU6Tb38S/YDvEhna0fcIr5wj
EYyyqf5m2hFsFqZoYonscZGzd6bT3wPOl/vXrY5AdDclQ/UqNDbCev2vIIQkuvRzpxrX
VMcg==
X-Received: by 10.70.37.207 with SMTP id a15mr12707986pdk.4.1437616418957;
Wed, 22 Jul 2015 18:53:38 -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 p1sm5595854pdb.3.2015.07.22.18.53.37
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Wed, 22 Jul 2015 18:53:37 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Content-Type: multipart/signed;
boundary="Apple-Mail=_C6B4FA20-98E1-4AD2-BFFB-6B752541E7EF";
protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b6
From: Eric Lombrozo <elombrozo@gmail.com>
In-Reply-To: <CA+w+GKQ_b0gMFov24nt8ZX89=GDWTpX9J15sj=fuicQBqBVcag@mail.gmail.com>
Date: Wed, 22 Jul 2015 18:53:36 -0700
Message-Id: <2795DFE0-C544-432D-BE01-6DEF7DC4FAB1@gmail.com>
References: <CAPg+sBgs-ouEMu=LOVCmOyCGwfM1Ygxooz0shyvAuHDGGZYfJw@mail.gmail.com>
<CAPg+sBgugLSVEwDLXhgey86_rM2fTjGWXFuXsiZioJKCZiHiNg@mail.gmail.com>
<CA+w+GKTfBNsQm0X27+QeMmLvJXuX0H=8+ij_GU6mkGnWn-poZA@mail.gmail.com>
<CAA33663-B688-4D53-8BED-85B4E67EFA0A@gmail.com>
<CA+w+GKQ_b0gMFov24nt8ZX89=GDWTpX9J15sj=fuicQBqBVcag@mail.gmail.com>
To: Mike Hearn <hearn@vinumeris.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@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin Core and hard forks
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, 23 Jul 2015 01:53:39 -0000
--Apple-Mail=_C6B4FA20-98E1-4AD2-BFFB-6B752541E7EF
Content-Type: multipart/alternative;
boundary="Apple-Mail=_6FB3D1E3-BF8D-4B59-9F7A-B2D64CF95A7C"
--Apple-Mail=_6FB3D1E3-BF8D-4B59-9F7A-B2D64CF95A7C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
> On Jul 22, 2015, at 3:01 PM, Mike Hearn <hearn@vinumeris.com> wrote:
>=20
> Until we=E2=80=99re able to merge blockchain forks like we=E2=80=99re =
able to merge git repo forks, the safest option is no fork.
>=20
> Block chain forks merge in the same way as git forks all the time, =
that's how the reorg algorithm works. Transactions that didn't make it =
into the post-reorg chain go back into the mempool and miners attempt to =
reinclude them: this is the "merge" process. If they now conflict with =
other transactions they are dropped and this is "resolving merge =
conflicts".
>=20
> However you have to want to merge with the new chain. If your software =
is programmed not to do that out of some bizarre belief that throttling =
your own user base is a good idea, then of course, no merge happens. =
Once you stop telling your computer to do that, you can then merge =
(reorg) back onto the main chain again.
>=20
Mike, you might be surprized to learn that there are other hard fork =
proposals out there besides increasing block size.
--Apple-Mail=_6FB3D1E3-BF8D-4B59-9F7A-B2D64CF95A7C
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""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
Jul 22, 2015, at 3:01 PM, Mike Hearn <<a =
href=3D"mailto:hearn@vinumeris.com" class=3D"">hearn@vinumeris.com</a>>=
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
dir=3D"ltr" class=3D""><div class=3D"gmail_extra"><div =
class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div =
style=3D"word-wrap:break-word" class=3D""><div class=3D""><div =
class=3D"">Until we=E2=80=99re able to merge blockchain forks like =
we=E2=80=99re able to merge git repo forks, the safest option is no =
fork.</div></div></div></blockquote><div class=3D""><br =
class=3D""></div><div class=3D"">Block chain forks merge in the same way =
as git forks all the time, that's how the reorg algorithm works. =
Transactions that didn't make it into the post-reorg chain go back into =
the mempool and miners attempt to reinclude them: this is the "merge" =
process. If they now conflict with other transactions they are dropped =
and this is "resolving merge conflicts".</div><div class=3D""><br =
class=3D""></div><div class=3D"">However you have to want to merge with =
the new chain. If your software is programmed not to do that out of some =
bizarre belief that throttling your own user base is a good idea, then =
of course, no merge happens. Once you stop telling your computer to do =
that, you can then merge (reorg) back onto the main chain =
again.</div><div class=3D""><br class=3D""></div></div></div></div>
</div></blockquote></div><br class=3D""><div class=3D"">Mike, you might =
be surprized to learn that there are other hard fork proposals out there =
besides increasing block size.<br class=3D""><div><blockquote =
type=3D"cite" class=3D""></blockquote></div></div><div class=3D""><br =
class=3D""></div></body></html>=
--Apple-Mail=_6FB3D1E3-BF8D-4B59-9F7A-B2D64CF95A7C--
--Apple-Mail=_C6B4FA20-98E1-4AD2-BFFB-6B752541E7EF
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
iQIcBAEBCgAGBQJVsEkgAAoJEJNAI64YFENUABwP/1Hkc/WO277S4d9wSDraIZZp
I/SzISaS8AaxIQ8ZPKpaU17I2GPNd54GhwMkpzRfgicfmNQp4JPWPCaxxUAvTJZq
ahfy/nnkCOSBoB66cd9M1wY08VKWHpz2/PKRKN51LJKzTdphha/KD1us5S28Zh5G
G7CE68h4k8h2DH/lDN3bd8rs1W4GNYMPdmP6VDJwDTZdQYDzH4K0exYV5mG87eVw
v+6ljVa1va3boITFQkm+k04ajwbaIQX1veLavlA0oQUta4Cw8VMnmPndir47oR8j
+KpqDBbtGwkf14E2vz/7cBpe2mdrYzikeVj4prSGuXpe7PCiJxw0tripytpt8XJr
U8keVsvxypF+pxiOX7ppvnw0oO+1fYzJP2dw3++JgQ8x9MPfQvXfts1unCjKIerM
nix10jMKJtpvI/bCgiHDmB42jL4RZQr3edmlBdkes0wyLCkrb5GbSUj48Zy+8500
fdQXmlKeujqw42Gx0Gg50dtGSv6l54tCeTaazeeF13cgNW+EzrBO3y66p3fn4JMj
sWCbnNMaIt8sBESmB6rf1pE9TyKsb7nT+njCdGSY+pLMiXDLY6f7FSuC6BTPMY3P
hS3hrStaWozTFzeEJXkQTbrsilvwBUVtHtk4qXrA62F7IB2tBqT16kcl7gazamkO
XEus2qjpGjPvh4FNmjES
=bMnt
-----END PGP SIGNATURE-----
--Apple-Mail=_C6B4FA20-98E1-4AD2-BFFB-6B752541E7EF--
|
