summaryrefslogtreecommitdiff
path: root/17/b0525ef5cc894e04b7a3acf60d2535b1139415
blob: 57e0ae5e5ed2fc009a5595036bd50788c3146724 (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
Return-Path: <hearn@vinumeris.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id C2C29360
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 22 Jul 2015 22:01:33 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ie0-f180.google.com (mail-ie0-f180.google.com
	[209.85.223.180])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 4A7EAE8
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 22 Jul 2015 22:01:33 +0000 (UTC)
Received: by iecri3 with SMTP id ri3so83316358iec.2
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 22 Jul 2015 15:01:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=vinumeris.com; s=google;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=DVzNGEbkpmFRz5aOAwkUiaflaEm2NiuAb9Nmgh8i2rs=;
	b=NOdk352xBY9b6j+HUxbhZtLdFR8Jm1SftgdUl0hUl+PXdkAry4+lxuZfizIG5Cq608
	6JssxBWpshaHg9SjCPXCb9xeswG8r9ogcV1nxOMRcjiYi8zNAlth1k3RqQ5j9Uwx3S9t
	IB/CoJuSC0mKWBfz9O9tSWY8DWyhTdiCDzhWc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:cc:content-type;
	bh=DVzNGEbkpmFRz5aOAwkUiaflaEm2NiuAb9Nmgh8i2rs=;
	b=A2GgbS3vetWFwHU2KFiuBjwyXgG9W4w1dDZq8/dkFKtBSRvVIq3RsTCwrUgOfen3sf
	ZVidILdc4Gort6tH7vfuPLz56euav0/vD3fzJzSakMoVb96mbBWB+OK3cO9KUkdKQfCQ
	+T/YTJuSFgnwea+k/G85lRpHhgzrz6I+a5d8XY2JbboBP/2qlYcdLXPcUgtaPyYaVwPw
	L6dQtRt9uZ07cdJzl3wbSfdN8PogB3yw7/gjVE/7rCJKkD62XL7xZRkME6GBujIU/Clh
	bCC0PbiZlCKFq8F4zDWUP4uobc5f87ZSOODAIQUuEIF7B+4AkeCJiZF1Dg6OXf8BX0kd
	crBg==
X-Gm-Message-State: ALoCoQme4g2z3FsNg3OiCNma6M1c481KvUt717RHELKuEk8aVjPO9FwPQfhi6C/R9gTOo0RTis2e
MIME-Version: 1.0
X-Received: by 10.107.40.147 with SMTP id o141mr7953491ioo.83.1437602492844;
	Wed, 22 Jul 2015 15:01:32 -0700 (PDT)
Received: by 10.50.108.111 with HTTP; Wed, 22 Jul 2015 15:01:32 -0700 (PDT)
In-Reply-To: <CAA33663-B688-4D53-8BED-85B4E67EFA0A@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>
Date: Thu, 23 Jul 2015 00:01:32 +0200
Message-ID: <CA+w+GKQ_b0gMFov24nt8ZX89=GDWTpX9J15sj=fuicQBqBVcag@mail.gmail.com>
From: Mike Hearn <hearn@vinumeris.com>
To: Eric Lombrozo <elombrozo@gmail.com>
Content-Type: multipart/alternative; boundary=001a1141d818ea2b44051b7de9a6
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,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: Wed, 22 Jul 2015 22:01:33 -0000

--001a1141d818ea2b44051b7de9a6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

>
> Until we=E2=80=99re able to merge blockchain forks like we=E2=80=99re abl=
e to merge git
> repo forks, the safest option is no fork.
>

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".

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.

--001a1141d818ea2b44051b7de9a6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><div><div>Un=
til 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></blo=
ckquote><div><br></div><div>Block chain forks merge in the same way as git =
forks all the time, that&#39;s how the reorg algorithm works. Transactions =
that didn&#39;t make it into the post-reorg chain go back into the mempool =
and miners attempt to reinclude them: this is the &quot;merge&quot; process=
. If they now conflict with other transactions they are dropped and this is=
 &quot;resolving merge conflicts&quot;.</div><div><br></div><div>However yo=
u 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 bas=
e is a good idea, then of course, no merge happens. Once you stop telling y=
our computer to do that, you can then merge (reorg) back onto the main chai=
n again.</div><div><br></div></div></div></div>

--001a1141d818ea2b44051b7de9a6--