summaryrefslogtreecommitdiff
path: root/81/5a91eb40b6d7cd514f8f582e935adb3368f49e
blob: dafe6d9ff90bcd1db15ab0342949e8d8d9f021ef (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
Return-Path: <jtimon@jtimon.cc>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 56FF0C2E
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed,  9 Dec 2015 00:58:08 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-vk0-f46.google.com (mail-vk0-f46.google.com
	[209.85.213.46])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id B9D56106
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed,  9 Dec 2015 00:58:07 +0000 (UTC)
Received: by vkha189 with SMTP id a189so33635321vkh.2
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 08 Dec 2015 16:58:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=jtimon-cc.20150623.gappssmtp.com; s=20150623;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=jl5pCFyrny0L9bV04AJOvfSehBVUCZim4ZvOKSn2Z9I=;
	b=GORCkP38/sVBB6M24w9fEwJXHo+vIa+AWjBakl/cP0Ohgrla16kUrYHHMrjDbn2oJH
	3lAAo2YqBnFP5vcm/j3tI+L1bBcN1HER0O1J+SlyXWdI19R+LcolL2CBmLQHJOP6448g
	SrRtO8kUp2GK5pln9/jnXwMfqPQ6Z3I3fqowzid+jfpYCCRXjByrFlYbYqzxjyODSKK4
	cn6d1+aYG8Xj9TF35gQhXBpPiWT+Y352fwULLqZwzYgfbBuksQhSNJT3PL0v4n5slEsA
	ccUVjUnz1888nV8NxptK+0EZXVoLhUdjPq1juS0OLjThZgNucdgFw+v8OdVYsT03itTy
	I/uA==
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=jl5pCFyrny0L9bV04AJOvfSehBVUCZim4ZvOKSn2Z9I=;
	b=S3U+KrS9GAIK660kaFSc2Yul8MScPY2VAue3CLm2W+kAwYAsY6IauYPsteKMvOlrke
	roEMTzGYDIHvOEGbROO19QYUKx4DIX5Vbj+OhdxEgDVhgJjry+uE5cef68iGxYkiI++1
	LMhedY9Zr8LTbMF6XlS2NqvDrELzwuSKzjkyNTYzp2dIiu3jOVkIw/Ruq/iQzvzhu9ha
	hDmSYCDCUlbsBNaZb+c9CIWLOVXpbLyYmoWJbnIVc17GN7qJo/0zG9HwV0Jjd9ZATe78
	LxH97oZ2ki/m4xKR6Pb/3lZkHMFFXaZ6yweTMLrNRyaf6nmxhw8UzK8FTyz4c9TcRDZs
	SMdw==
X-Gm-Message-State: ALoCoQkmIRmTXNC1gonGoV+xaH9lg6oesZr+prw7BVBt6eFPyGaNXTCZsqRkr1uRj/bGS1TCXSp8M4LAPbxBZMfgaJT9n5OYlg==
MIME-Version: 1.0
X-Received: by 10.31.16.197 with SMTP id 66mr2254466vkq.143.1449622687041;
	Tue, 08 Dec 2015 16:58:07 -0800 (PST)
Received: by 10.31.236.70 with HTTP; Tue, 8 Dec 2015 16:58:06 -0800 (PST)
In-Reply-To: <CAAS2fgTGYSiAJHZq80rD4UieV8XetS=W0b45b5onWAS9gF-F7g@mail.gmail.com>
References: <CAAS2fgQyVs1fAEj+vqp8E2=FRnqsgs7VUKqALNBHNxRMDsHdVg@mail.gmail.com>
	<20151208110752.GA31180@amethyst.visucore.com>
	<CABm2gDpcek=u=Rpe68EMOq6M7Bji9J=s5VvoQWKRqaQDAP5kTw@mail.gmail.com>
	<CABsx9T1wga3Tandoe2mVGSKdHJytHoc9Ko7HRm2SvJXABEFk9w@mail.gmail.com>
	<CAAS2fgTGYSiAJHZq80rD4UieV8XetS=W0b45b5onWAS9gF-F7g@mail.gmail.com>
Date: Wed, 9 Dec 2015 01:58:06 +0100
Message-ID: <CABm2gDrb4ka_sYG-jRzg=gqWvtxLysbRxXCLYL+F5HMqDP0jGg@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Gregory Maxwell <greg@xiph.org>
Content-Type: text/plain; charset=UTF-8
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,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] Capacity increases for the Bitcoin system.
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, 09 Dec 2015 00:58:08 -0000

On Wed, Dec 9, 2015 at 12:59 AM, Gregory Maxwell via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> On Tue, Dec 8, 2015 at 3:12 PM, Gavin Andresen via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
> We already have consensus critical enforcement there, the height,
> which has almost never been problematic. (A popular block explorer
> recently misimplemented the var-int decode and suffered an outage).

It would be also a nice opportunity to move the height to a more
accessible place.
For example CBlockHeader::hashMerkleRoot (and CBlockIndex's) could be
replaced with a hash of the following struct:

struct hashRootStruct
{
uint256 hashMerkleRoot;
uint256 hashWitnessesRoot;
int32_t nHeight;
}

> From a risk reduction perspective, I think it is much preferable to
> perform the primary change in a backwards compatible manner, and pick
> up the data reorganization in a hardfork if anyone even cares.


But then all wallet software will need to adapt their software twice.
Why introduce technical debt for no good reason?

> I think thats generally a nice cadence to split up risks that way; and
> avoid controversy.

Uncontroversial hardforks can also be deployed with small risks as
described in BIP99.