Message-ID: <1327681998.52230.YahooMailNeo@web121001.mail.ne1.yahoo.com>
Date: Fri, 27 Jan 2012 08:33:18 -0800 (PST)
From: Amir Taaki <zgenjix@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="344044665-1665659227-1327681998=:52230"
Subject: [Bitcoin-development] GetBlocksToMaturity
Precedence: list
Reply-To: Amir Taaki <zgenjix@yahoo.com>

--344044665-1665659227-1327681998=:52230
Content-Type: text/plain; charset=us-ascii

Why add 20 to COINBASE_MATURITY there?

The underlying protocol accepts spent transactions at 100 (COINBASE_MATURITY) so this seems more like a measure to put people off spending until 120 confirms. If you are determined enough to hack your client, you can still spend before 120 but after 100.

Why is this?

Did Satoshi overestimate how many competing races there would be between mined blocks?
--344044665-1665659227-1327681998=:52230
Content-Type: text/html; charset=us-ascii

<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div>Why add 20 to COINBASE_MATURITY there?</div><div><br></div><div>The underlying protocol accepts spent transactions at 100 (COINBASE_MATURITY) so this seems more like a measure to put people off spending until 120 confirms. If you are determined enough to hack your client, you can still spend before 120 but after 100.</div><div><br></div><div>Why is this?</div><div><br></div><div>Did Satoshi overestimate how many competing races there would be between mined blocks?</div></div></body></html>
--344044665-1665659227-1327681998=:52230--