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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mark@monetize.io>) id 1SnCHi-0006Yn-Kg
for bitcoin-development@lists.sourceforge.net;
Fri, 06 Jul 2012 17:25:38 +0000
Received: from mail-gh0-f175.google.com ([209.85.160.175])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1SnCHh-0000ny-SN
for bitcoin-development@lists.sourceforge.net;
Fri, 06 Jul 2012 17:25:38 +0000
Received: by ghbz2 with SMTP id z2so9043325ghb.34
for <bitcoin-development@lists.sourceforge.net>;
Fri, 06 Jul 2012 10:25:32 -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=dLkMLJjN03MZ0Hl56n7eJznk0BOSb5S4POtAh9jOXzw=;
b=jK3fAGCWoG8fOBnwyDUmPj+oxCC+Kd5nohtQcuAJSvAimyyDQHxHuNLDzH8X/TG3Qu
mBnieE9obxEPVTAnMWPWUEjdayAaT072DOOM9p7q6YDmIhLANXNmJb34gFufFwvjDD+n
40bWGupACm7MyzKsTDkPvlGSIS2mGH5iziNC7nnAXIl36Jb1AFTWlyWrEc1XALs7Nw7K
90fjaFHmXVyVFv+4KXnV/2hD3hRqZ8y9mNTYyujNw8ZA2rfr4N5ERko4rYb49oyROL00
CmhDGF3J1YIxn49yEghm8DIcm7/aj18VXvbFkW3D9a0dna5zSdI+3TY51LUce8woesKl
XO4g==
MIME-Version: 1.0
Received: by 10.60.172.143 with SMTP id bc15mr31795350oec.73.1341593776548;
Fri, 06 Jul 2012 09:56:16 -0700 (PDT)
Received: by 10.76.101.167 with HTTP; Fri, 6 Jul 2012 09:56:16 -0700 (PDT)
X-Originating-IP: [50.0.36.54]
In-Reply-To: <CA+8xBpdbgkzwOvyUsJYEXNMTBwuvAbFsKx2xF1s0BMPiL9n1Qw@mail.gmail.com>
References: <CA+8xBpefOgtuECJqoAtbFfPnmkFEHTL=6Uqf=kb7NB=fnV863Q@mail.gmail.com>
<CAMGNxUsZQMN+M4cR8nMhNmJAAnT2ZSPjrMHV0BetdiMmj453sA@mail.gmail.com>
<CA+8xBpdbgkzwOvyUsJYEXNMTBwuvAbFsKx2xF1s0BMPiL9n1Qw@mail.gmail.com>
Date: Fri, 6 Jul 2012 09:56:16 -0700
Message-ID: <CACh7GpFb8Xxn9KmR34UNw6N=P96TJSgqec+eLdr5KneZAOj9Tw@mail.gmail.com>
From: Mark Friedenbach <mark@monetize.io>
To: Jeff Garzik <jgarzik@exmulti.com>
Content-Type: multipart/alternative; boundary=bcaec54c527c7beccd04c42c24ed
X-Gm-Message-State: ALoCoQmwHViTw2CJKds9WdkXdj6ax8ZEKzXwHRYRbnWbdSqlodfxjAUtYi/etYlR11CwivDy8GTI
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1SnCHh-0000ny-SN
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 17:25:38 -0000
--bcaec54c527c7beccd04c42c24ed
Content-Type: text/plain; charset=UTF-8
On Fri, Jul 6, 2012 at 9:49 AM, Jeff Garzik <jgarzik@exmulti.com> wrote:
> 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.
>
But those issues are solvable through other, non-backwards incompatible
means. For example, mandate that a <transaction hash, output index> refers
to the first such pair that is not already spent. No?
Mark
--bcaec54c527c7beccd04c42c24ed
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On Fri, Jul 6, 2012 at 9:49 AM, Jeff Garzik <span dir=3D"ltr"><<a href=
=3D"mailto:jgarzik@exmulti.com" target=3D"_blank">jgarzik@exmulti.com</a>&g=
t;</span> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">
On Fri, Jul 6, 2012 at 12:45 PM, Peter Vessenes <<a href=3D"mailto:peter=
@coinlab.com">peter@coinlab.com</a>> wrote:<br>
> The proposal is simple, and it's a small change for miners, I imag=
ine.<br>
><br>
> My question is: why?<br>
><br>
> I worry about stuffing too many requirements on the coinbase. I suppos=
e<br>
> the coinbase is easily extendible if we run out of bytes, but I think =
I'd<br>
> like to see some more discussion / good / bad type cases for making th=
is<br>
> change. What do we get over just the prev_hash by doing this?<br>
<br>
With the existing setup (sans height in coinbase), you might not have<br>
unique transactions, with all that entails.<br></blockquote><div><br></div>=
<div>But those issues are solvable through other, non-backwards incompatibl=
e means. For example, mandate that a <transaction hash, output index>=
refers to the first such pair that is not already spent. No?</div>
<div><br></div><div>Mark</div></div>
--bcaec54c527c7beccd04c42c24ed--
|
