summaryrefslogtreecommitdiff
path: root/0c/3ac7115b35dc9c19432c0825f10a85732fc256
blob: 6f94a18e1849f98783fce27e4c7144f82aeb1a56 (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
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <jgarzik@exmulti.com>) id 1SnBia-0003hC-BI
	for bitcoin-development@lists.sourceforge.net;
	Fri, 06 Jul 2012 16:49:20 +0000
X-ACL-Warn: 
Received: from mail-lb0-f175.google.com ([209.85.217.175])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1SnBiY-00089F-VX
	for bitcoin-development@lists.sourceforge.net;
	Fri, 06 Jul 2012 16:49:20 +0000
Received: by lbol5 with SMTP id l5so14542405lbo.34
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 06 Jul 2012 09:49:12 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:in-reply-to:references:date
	:message-id:subject:from:to:cc:content-type:x-gm-message-state;
	bh=I+dY34Xnnqp+wzI4S9dCcXAHBX020jsSzBi/cTSKeDg=;
	b=clqRbn07efNxh/X48kp+e2P5wJJhxtqeVuU7rYSOZG5Ee5P/tL1e8WhZLVqIBH83w1
	xYrprP1kj4zvGBVfWazNk0mpASCzNswJV7JJsyoTi20oJd1JPHGJ6W6COEKN7Nzg5X6G
	Kym//YiKTOwdUaf9zS3oGef3dYudh+zrAHfgWjLmUn82ISknTpzSyKrfZYfADMViovve
	xJ0TvOXxSpnW6mQp0Qt1BXYzOCTGcwPx8xJOCOWLsc0tvYHv3i4ZC3gOEKudV+vEpMoX
	ubrGCFGigcHVTctDJqTO47NzN54j7x5Vav+y8cdcwjZQWgRjATXd7fAdiPUTXsyJOML8
	Ioyw==
MIME-Version: 1.0
Received: by 10.152.131.68 with SMTP id ok4mr30589076lab.47.1341593352415;
	Fri, 06 Jul 2012 09:49:12 -0700 (PDT)
Received: by 10.114.63.165 with HTTP; Fri, 6 Jul 2012 09:49:12 -0700 (PDT)
X-Originating-IP: [2001:4830:1603:2:21c:c0ff:fe79:c8c2]
In-Reply-To: <CAMGNxUsZQMN+M4cR8nMhNmJAAnT2ZSPjrMHV0BetdiMmj453sA@mail.gmail.com>
References: <CA+8xBpefOgtuECJqoAtbFfPnmkFEHTL=6Uqf=kb7NB=fnV863Q@mail.gmail.com>
	<CAMGNxUsZQMN+M4cR8nMhNmJAAnT2ZSPjrMHV0BetdiMmj453sA@mail.gmail.com>
Date: Fri, 6 Jul 2012 12:49:12 -0400
Message-ID: <CA+8xBpdbgkzwOvyUsJYEXNMTBwuvAbFsKx2xF1s0BMPiL9n1Qw@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: Peter Vessenes <peter@coinlab.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQmxMAMNrLVJoUfDjVlPM56nFAvvFhwMVrXb6TTSqrQshwk8Tla5qV+/+4GYI6r7CvHGIoaP
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1SnBiY-00089F-VX
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP 34: Block v2, Height in Coinbase
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: Fri, 06 Jul 2012 16:49:20 -0000

On Fri, Jul 6, 2012 at 12:45 PM, Peter Vessenes <peter@coinlab.com> wrote:
> The proposal is simple, and it's a small change for miners, I imagine.
>
> My question is: why?
>
> I worry about stuffing too many requirements on the coinbase. I suppose
> the coinbase is easily extendible if we run out of bytes, but I think I'd
> like to see some more discussion / good / bad type cases for making this
> change. What do we get over just the prev_hash by doing this?

With the existing setup (sans height in coinbase), you might not have
unique transactions, with all that entails.

> Anyway, some background would be great; if I missed it, I'm happy to go
> read up, but I didn't see any links on the wiki.

Gavin wrote some notes on upgrades and BIP16 lessons-learned at
https://gist.github.com/2355445

--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com