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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <zgenjix@yahoo.com>) id 1SnEjn-0003Vu-9n
for bitcoin-development@lists.sourceforge.net;
Fri, 06 Jul 2012 20:02:47 +0000
X-ACL-Warn:
Received: from nm10.bullet.mail.ne1.yahoo.com ([98.138.90.73])
by sog-mx-1.v43.ch3.sourceforge.com with smtp (Exim 4.76)
id 1SnEjm-0005Zl-CX for bitcoin-development@lists.sourceforge.net;
Fri, 06 Jul 2012 20:02:47 +0000
Received: from [98.138.90.48] by nm10.bullet.mail.ne1.yahoo.com with NNFMP;
06 Jul 2012 20:02:40 -0000
Received: from [98.138.89.232] by tm1.bullet.mail.ne1.yahoo.com with NNFMP;
06 Jul 2012 20:02:40 -0000
Received: from [127.0.0.1] by omp1047.mail.ne1.yahoo.com with NNFMP;
06 Jul 2012 20:02:40 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 871537.96826.bm@omp1047.mail.ne1.yahoo.com
Received: (qmail 85634 invoked by uid 60001); 6 Jul 2012 20:02:40 -0000
X-YMail-OSG: MmLGFEkVM1nFOGs8KnTxs.uMaJAycxWMUYHSC7sQdPt49uU
lk4.wzGLMnsGBVElaYcEqy5WbXxNGH4B4Dh62GgTD_Sucy4eQKOYEIWjL00K
7DzDTHXq3FGMhWGr28XRDE5b8QulZ5UIMEzQxSg51ZR08E09NfTkmaaSaN2o
SCwOf_AF33_tihaj07Xjf8.TuVzFTfF56K9tlJdTZ5Mlfm12oJRN76eNm5gB
iooji8sBgkhIMTyhyVMqLjAWJY0BtSl5xhvQYBbdyEKtohjvjtFfIBp8XD4_
cBacX7lDd6D_3_vE1ZTT7GNaD2RO9FUfv4DMH_f7L1byybdaTcfxzNKwz1NC
Uo9widn7.8gjqYYTAxPiHHfEL.FAwNOtkYooM.j8ko0IG4zC4oX.AenEHcko
HIeix517yHanxCfnLA9DrPwjKRq_3wHm7hb2z8afAxgNyzUfvEvr_lkwzq_c
zy.bb_h5XIC5KEidAbQBvUQfQnfw6ho9OuRqYu2oFLKU4dg8l1f7GDZ2.Ete
zeOMAB_SzCA--
Received: from [178.5.23.109] by web121006.mail.ne1.yahoo.com via HTTP;
Fri, 06 Jul 2012 13:02:40 PDT
X-Mailer: YahooMailWebService/0.8.120.356233
References: <CA+8xBpefOgtuECJqoAtbFfPnmkFEHTL=6Uqf=kb7NB=fnV863Q@mail.gmail.com>
<CAMGNxUsZQMN+M4cR8nMhNmJAAnT2ZSPjrMHV0BetdiMmj453sA@mail.gmail.com>
<CA+8xBpdbgkzwOvyUsJYEXNMTBwuvAbFsKx2xF1s0BMPiL9n1Qw@mail.gmail.com>
<CACh7GpFb8Xxn9KmR34UNw6N=P96TJSgqec+eLdr5KneZAOj9Tw@mail.gmail.com>
Message-ID: <1341604960.84829.YahooMailNeo@web121006.mail.ne1.yahoo.com>
Date: Fri, 6 Jul 2012 13:02:40 -0700 (PDT)
From: Amir Taaki <zgenjix@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
In-Reply-To: <CACh7GpFb8Xxn9KmR34UNw6N=P96TJSgqec+eLdr5KneZAOj9Tw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: -0.1 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [98.138.90.73 listed in list.dnswl.org]
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(zgenjix[at]yahoo.com)
-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
0.0 FSL_FREEMAIL_2 FSL_FREEMAIL_2
0.0 FSL_FREEMAIL_1 FSL_FREEMAIL_1
X-Headers-End: 1SnEjm-0005Zl-CX
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
Reply-To: Amir Taaki <zgenjix@yahoo.com>
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 20:02:47 -0000
It would be nice if Bitcoin was engineered this way from the start. The amount of workarounds, special cases and code bloat to deal with the fact that txs are non-unique was a massive headache for me.
________________________________
From: Mark Friedenbach <mark@monetize.io>
To: Jeff Garzik <jgarzik@exmulti.com>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Sent: Friday, July 6, 2012 6:56 PM
Subject: Re: [Bitcoin-development] BIP 34: Block v2, Height in Coinbase
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
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development
|
