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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <tadas.varanavicius@gmail.com>) id 1UFBAO-0008Te-I1
for bitcoin-development@lists.sourceforge.net;
Mon, 11 Mar 2013 22:26:00 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.83.51 as permitted sender)
client-ip=74.125.83.51;
envelope-from=tadas.varanavicius@gmail.com;
helo=mail-ee0-f51.google.com;
Received: from mail-ee0-f51.google.com ([74.125.83.51])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UFBAN-00040f-OK
for bitcoin-development@lists.sourceforge.net;
Mon, 11 Mar 2013 22:26:00 +0000
Received: by mail-ee0-f51.google.com with SMTP id d17so2403349eek.10
for <bitcoin-development@lists.sourceforge.net>;
Mon, 11 Mar 2013 15:25:53 -0700 (PDT)
X-Received: by 10.15.23.193 with SMTP id h41mr41152289eeu.17.1363040753482;
Mon, 11 Mar 2013 15:25:53 -0700 (PDT)
Received: from [192.168.0.100] ([78.63.237.16])
by mx.google.com with ESMTPS id 46sm26078945eea.3.2013.03.11.15.25.52
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Mon, 11 Mar 2013 15:25:52 -0700 (PDT)
Message-ID: <513E59EE.7070605@gmail.com>
Date: Tue, 12 Mar 2013 00:25:50 +0200
From: =?UTF-8?B?VGFkYXMgVmFyYW5hdmnEjWl1cw==?= <tadas.varanavicius@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:17.0) Gecko/20130221 Thunderbird/17.0.3
MIME-Version: 1.0
To: Mike Hearn <mike@plan99.net>
References: <20130310043155.GA20020@savin>
<CABOyFfp9Kd+y=SofWfq6TiR4+xeOhFL7VVHWjtrRn83HMsmPBA@mail.gmail.com>
<CABsx9T1rt+7BQHz1S=NVtL_YV7kfCapQ+3MEf+xyXT7pZOfq7w@mail.gmail.com>
<CABOyFfrO9Xpc=Pdh_6AM1yoHRCeuHxzqL02F-ALkimmsGbheiA@mail.gmail.com>
<CABOyFfqh_VixG7SQMaQUkxU40MGY1f9JO3=OqwitHa1YoT4chQ@mail.gmail.com>
<CANEZrP0gsrd2W3ODfQRSc2k5V7GotJ0vzEAxcAjnaMtDHZ9_JA@mail.gmail.com>
<75F78378-7580-4D69-A5EA-E943AF7CEB0C@benlabs.net>
<513E2BC6.2050102@gmail.com>
<CANEZrP1tYTDf6k76=jcBL+10MpCgemV2TP=wZiRuA02vhUP78A@mail.gmail.com>
In-Reply-To: <CANEZrP1tYTDf6k76=jcBL+10MpCgemV2TP=wZiRuA02vhUP78A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.6 (-)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(tadas.varanavicius[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-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
X-Headers-End: 1UFBAN-00040f-OK
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Blocking uneconomical UTXO creation
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: Mon, 11 Mar 2013 22:26:00 -0000
On 03/12/2013 12:19 AM, Mike Hearn wrote:
> Firstly, the UTXO set is a LevelDB, it's not stored in memory. Outputs
> that never get spent are not in the working set by definition, after a
> while they just end up in the bottom levels and hardly ever get
> accessed. If need be we can always help LevelDB out a bit by moving
> outputs that we suspect are unlikely to get spent into a separate
> database, but I doubt it's needed.
Isn't there danger of an attack if UTXO is not stored in fast storage?
|
