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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <zgenjix@yahoo.com>) id 1Rqojs-0007ol-SC
for bitcoin-development@lists.sourceforge.net;
Fri, 27 Jan 2012 16:33:24 +0000
X-ACL-Warn:
Received: from nm11-vm1.bullet.mail.ne1.yahoo.com ([98.138.91.40])
by sog-mx-2.v43.ch3.sourceforge.com with smtp (Exim 4.76)
id 1Rqojs-0002eE-2M for bitcoin-development@lists.sourceforge.net;
Fri, 27 Jan 2012 16:33:24 +0000
Received: from [98.138.90.50] by nm11.bullet.mail.ne1.yahoo.com with NNFMP;
27 Jan 2012 16:33:18 -0000
Received: from [98.138.89.171] by tm3.bullet.mail.ne1.yahoo.com with NNFMP;
27 Jan 2012 16:33:18 -0000
Received: from [127.0.0.1] by omp1027.mail.ne1.yahoo.com with NNFMP;
27 Jan 2012 16:33:18 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 574882.53384.bm@omp1027.mail.ne1.yahoo.com
Received: (qmail 10838 invoked by uid 60001); 27 Jan 2012 16:33:18 -0000
X-YMail-OSG: ag0VK1oVM1mDZFMs8R8M4d.K_vgVPYlbnnqBc6YtbeA8k2S
68NFL6feuIE581U15MNpGfgJe7h.S9CEErR1GucPWtXsFlaMIONDnznELQad
oB_OgAN1hcUhOEenuaZRY4buMlltQG_Bl1cJmzkV53J6JOPQexJlQFCZ8a.Y
6BuO50wNx8uMRmBRJwE6NyTgMO.qGnuJ.VyIEyl7PuhgbTRu._0VSNCPqpcy
x41GpvLdyb8WGsYoZi5QtoF9mpswIQ2N0RvtXiRg9.lOuvdwmfQDpfL9WA.O
ePQp8gNSMPK8Lwaq2H7y5LlDoN08wuqGp0POYZ4uL2YbVyvYtF6YO73mTxcI
aftGoKkIo2lnC4RCX199cSGlL3J.nNfuZXAhW84I.u_o7ht12Xx9.GE3Cdg- -
Received: from [92.20.138.208] by web121001.mail.ne1.yahoo.com via HTTP;
Fri, 27 Jan 2012 08:33:18 PST
X-Mailer: YahooMailWebService/0.8.116.331537
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"
X-Spam-Score: 0.4 (/)
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.91.40 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 1.0 HTML_MESSAGE BODY: HTML included in message
-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.5 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1Rqojs-0002eE-2M
Subject: [Bitcoin-development] GetBlocksToMaturity
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, 27 Jan 2012 16:33:24 -0000
--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--
|
