path: root/bb/e570b05ee8538aa4c7198050645da671f5ce2a

Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <peter@coinlab.com>) id 1SnC3F-0004TS-8j
	for bitcoin-development@lists.sourceforge.net;
	Fri, 06 Jul 2012 17:10:41 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of coinlab.com
	designates 209.85.214.47 as permitted sender)
	client-ip=209.85.214.47; envelope-from=peter@coinlab.com;
	helo=mail-bk0-f47.google.com; 
Received: from mail-bk0-f47.google.com ([209.85.214.47])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1SnC3E-0001lD-00
	for bitcoin-development@lists.sourceforge.net;
	Fri, 06 Jul 2012 17:10:41 +0000
Received: by bkcik5 with SMTP id ik5so5404398bkc.34
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 06 Jul 2012 10:10:33 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type:x-gm-message-state;
	bh=jQcZe0I02AWUChmdKO32mlA4eAF6TDA52Ls9l7gtULs=;
	b=Fsvq1WRg0PJ89HNxt3PZQfiNr3agAUvKhqhe5qa2c/B9rnxNfqyDDXe5a10WR558eY
	sttg0V7t0KXPfiDUmkJ/RO6/JwydIGJLcxCcgEEbCexCbGj734wyCs8FnAeCatv/e2/O
	4uVMFAHV4DMsXkL9Yp+K0cmhNlNcBJiTtJTzFGRWgVzlf0+j/nKzDR5qOe4eF1+r7w+z
	V6jeYuXkukaViKlGa1AQ7HY01rQMNWOR7iuwziK+JIK40TlV0WrqMTa3VwUovAph1d5E
	5Jf2Hbf93gX/jXF2QK44tiYo7sSCHX4Yq4jrNTVMpIdLvy7kTNuoSvrX2Ay8570ygAOS
	wxLQ==
Received: by 10.152.148.195 with SMTP id tu3mr30923213lab.16.1341593121639;
	Fri, 06 Jul 2012 09:45:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.11.101 with HTTP; Fri, 6 Jul 2012 09:45:01 -0700 (PDT)
In-Reply-To: <CA+8xBpefOgtuECJqoAtbFfPnmkFEHTL=6Uqf=kb7NB=fnV863Q@mail.gmail.com>
References: <CA+8xBpefOgtuECJqoAtbFfPnmkFEHTL=6Uqf=kb7NB=fnV863Q@mail.gmail.com>
From: Peter Vessenes <peter@coinlab.com>
Date: Fri, 6 Jul 2012 09:45:01 -0700
Message-ID: <CAMGNxUsZQMN+M4cR8nMhNmJAAnT2ZSPjrMHV0BetdiMmj453sA@mail.gmail.com>
To: Jeff Garzik <jgarzik@exmulti.com>
Content-Type: multipart/alternative; boundary=e89a8f23485572cd6e04c42bfd96
X-Gm-Message-State: ALoCoQl4DBEeyDvd9hLbAV1ax7LDPqUkDO+q9nMMXzPHItzmPy4qN9T7XCGfk8jG0fQe5gy1D8TJ
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	0.0 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1SnC3E-0001lD-00
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:10:41 -0000

--e89a8f23485572cd6e04c42bfd96
Content-Type: text/plain; charset=ISO-8859-1

So,

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?

If this is just a voting mechanism for moving to v2 blocks, that's cool,
but it would be nice to codify voting in the coinbase a bit? Maybe? We've
now once voted with /p2sh/ and this is a different mechanism now, if I
understand it properly.

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.

Peter

On Fri, Jul 6, 2012 at 8:10 AM, Jeff Garzik <jgarzik@exmulti.com> wrote:

> Please review and comment...
>
> Block v2, Height in Coinbase
> https://en.bitcoin.it/wiki/BIP_0034
>
>   BIP: 34
>   Title: Block v2, Height in Coinbase
>   Author: Gavin Andresen <gavinandresen@gmail.com>
>   Status: Draft
>   Type: Standards Track
>   Created: 2012-07-06
>
> Abstract
>
> Bitcoin blocks and transactions are versioned binary structures. Both
> currently use version 1. This BIP introduces an upgrade path for
> versioned transactions and blocks. A unique nonce is added to newly
> produced coinbase transactions, and blocks are updated to version 2.
>
>
> Motivation
>
> 1.    Clarify and exercise the mechanism whereby the bitcoin network
> collectively consents to upgrade transaction or block binary
> structures, rules and behaviors.
>
> 2.    Enforce block and transaction uniqueness, and assist unconnected
> block validation.
>
>
> Specification
>
> 1.    Treat transactions with a version greater than 1 as non-standard
> (official Satoshi client will not mine or relay them).
>
> 2.    Add height as the first item in the coinbase transaction's
> scriptSig, and increase block version to 2. The format of the height
> is "serialized CScript" -- first byte is number of bytes in the number
> (will be 0x03 on main net for the next 300 or so years), following
> bytes are little-endian representation of the number.
>
> 3.    75% rule: If 750 of the last 1,000 blocks are version 2 or
> greater, reject invalid version 2 blocks. (testnet3: 51 of last 100)
>
> 4.    95% rule ("Point of no return"): If 950 of the last 1,000 blocks
> are version 2 or greater, reject all version 1 blocks. (testnet3: 75
> of last 100)
>
>
> Backward compatibility
>
> All older clients are compatible with this change. Users and merchants
> should not be impacted. Miners are strongly recommended to upgrade to
> version 2 blocks. Once 95% of the miners have upgraded to version 2,
> the remainder will be orphaned if they fail to upgrade.
>
>
> Implementation
>
> https://github.com/bitcoin/bitcoin/pull/1525 and
> https://github.com/bitcoin/bitcoin/pull/1526
>
> --
> Jeff Garzik
> exMULTI, Inc.
> jgarzik@exmulti.com
>
>
> ------------------------------------------------------------------------------
> 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
>



-- 
------------------------------

[image: CoinLab Logo]PETER VESSENES
CEO

*peter@coinlab.com * /  206.486.6856  / SKYPE: vessenes
811 FIRST AVENUE  /  SUITE 480  /  SEATTLE, WA 98104

--e89a8f23485572cd6e04c42bfd96
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

So,=A0<div><br></div><div>The proposal is simple, and it&#39;s a small chan=
ge for miners, I imagine.=A0</div><div><br></div><div>My question is: why?=
=A0</div><div><br></div><div>I worry about stuffing too many requirements o=
n the coinbase. I suppose the coinbase is easily extendible if we run out o=
f bytes, but I think I&#39;d like to see some more discussion / good / bad =
type cases for making this change. What do we get over just the prev_hash b=
y doing this?=A0</div>

<div><br></div><div>If this is just a voting mechanism for moving to v2 blo=
cks, that&#39;s cool, but it would be nice to codify voting in the coinbase=
 a bit? Maybe? We&#39;ve now once voted with /p2sh/ and this is a different=
 mechanism now, if I understand it properly.=A0</div>

<div><br></div><div>Anyway, some background would be great; if I missed it,=
 I&#39;m happy to go read up, but I didn&#39;t see any links on the wiki.</=
div><div><br></div><div>Peter</div><div><br><div class=3D"gmail_quote">On F=
ri, Jul 6, 2012 at 8:10 AM, Jeff Garzik <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:jgarzik@exmulti.com" target=3D"_blank">jgarzik@exmulti.com</a>&gt;</sp=
an> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Please review and comment...<br>
<br>
Block v2, Height in Coinbase<br>
<a href=3D"https://en.bitcoin.it/wiki/BIP_0034" target=3D"_blank">https://e=
n.bitcoin.it/wiki/BIP_0034</a><br>
<br>
=A0 BIP: 34<br>
=A0 Title: Block v2, Height in Coinbase<br>
=A0 Author: Gavin Andresen &lt;<a href=3D"mailto:gavinandresen@gmail.com">g=
avinandresen@gmail.com</a>&gt;<br>
=A0 Status: Draft<br>
=A0 Type: Standards Track<br>
=A0 Created: 2012-07-06<br>
<br>
Abstract<br>
<br>
Bitcoin blocks and transactions are versioned binary structures. Both<br>
currently use version 1. This BIP introduces an upgrade path for<br>
versioned transactions and blocks. A unique nonce is added to newly<br>
produced coinbase transactions, and blocks are updated to version 2.<br>
<br>
<br>
Motivation<br>
<br>
1. =A0 =A0Clarify and exercise the mechanism whereby the bitcoin network<br=
>
collectively consents to upgrade transaction or block binary<br>
structures, rules and behaviors.<br>
<br>
2. =A0 =A0Enforce block and transaction uniqueness, and assist unconnected<=
br>
block validation.<br>
<br>
<br>
Specification<br>
<br>
1. =A0 =A0Treat transactions with a version greater than 1 as non-standard<=
br>
(official Satoshi client will not mine or relay them).<br>
<br>
2. =A0 =A0Add height as the first item in the coinbase transaction&#39;s<br=
>
scriptSig, and increase block version to 2. The format of the height<br>
is &quot;serialized CScript&quot; -- first byte is number of bytes in the n=
umber<br>
(will be 0x03 on main net for the next 300 or so years), following<br>
bytes are little-endian representation of the number.<br>
<br>
3. =A0 =A075% rule: If 750 of the last 1,000 blocks are version 2 or<br>
greater, reject invalid version 2 blocks. (testnet3: 51 of last 100)<br>
<br>
4. =A0 =A095% rule (&quot;Point of no return&quot;): If 950 of the last 1,0=
00 blocks<br>
are version 2 or greater, reject all version 1 blocks. (testnet3: 75<br>
of last 100)<br>
<br>
<br>
Backward compatibility<br>
<br>
All older clients are compatible with this change. Users and merchants<br>
should not be impacted. Miners are strongly recommended to upgrade to<br>
version 2 blocks. Once 95% of the miners have upgraded to version 2,<br>
the remainder will be orphaned if they fail to upgrade.<br>
<br>
<br>
Implementation<br>
<br>
<a href=3D"https://github.com/bitcoin/bitcoin/pull/1525" target=3D"_blank">=
https://github.com/bitcoin/bitcoin/pull/1525</a> and<br>
<a href=3D"https://github.com/bitcoin/bitcoin/pull/1526" target=3D"_blank">=
https://github.com/bitcoin/bitcoin/pull/1526</a><br>
<br>
--<br>
Jeff Garzik<br>
exMULTI, Inc.<br>
<a href=3D"mailto:jgarzik@exmulti.com">jgarzik@exmulti.com</a><br>
<br>
---------------------------------------------------------------------------=
---<br>
Live Security Virtual Conference<br>
Exclusive live event will cover all the ways today&#39;s security and<br>
threat landscape has changed and how IT managers can respond. Discussions<b=
r>
will include endpoint security, mobile security and the latest in malware<b=
r>
threats. <a href=3D"http://www.accelacomm.com/jaw/sfrnl04242012/114/5012226=
3/" target=3D"_blank">http://www.accelacomm.com/jaw/sfrnl04242012/114/50122=
263/</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><hr style=3D=
"font-family:Times;font-size:medium;border-right-width:0px;border-bottom-wi=
dth:0px;border-left-width:0px;border-top-style:solid;border-top-color:rgb(2=
04,204,204);margin:10px 0px">

<p style=3D"font-size:medium;font-family:Helvetica,sans-serif;line-height:1=
em"><span style=3D"color:rgb(50,90,135);text-transform:uppercase"><img src=
=3D"http://coinlab.com/static/images/email_logo.jpg" align=3D"right" alt=3D=
"CoinLab Logo" width=3D"130">PETER=A0<span style=3D"font-weight:bold">VESSE=
NES=A0</span><br>

<span style=3D"color:rgb(96,58,23);font-size:0.8em">CEO</span></span></p><p=
 style=3D"font-size:medium;font-family:Helvetica,sans-serif;line-height:1em=
"><span style=3D"color:rgb(96,58,23);font-size:0.9em"><strong><a href=3D"ma=
ilto:peter@coinlab.com" style=3D"text-decoration:none;color:rgb(96,58,23)" =
target=3D"_blank">peter@coinlab.com</a>=A0</strong>=A0/=A0=A0206.486.6856 =
=A0/=A0<span style=3D"font-size:0.7em;text-transform:uppercase">SKYPE:</spa=
n>=A0vessenes=A0</span><br>

<span style=3D"color:rgb(96,58,23);font-size:0.7em;text-transform:uppercase=
">811 FIRST AVENUE =A0/=A0 SUITE 480 =A0/=A0 SEATTLE, WA 98104</span></p><b=
r>
</div>

--e89a8f23485572cd6e04c42bfd96--