From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UFC6j-0003m7-Ps for bitcoin-development@lists.sourceforge.net; Mon, 11 Mar 2013 23:26:17 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.83.52 as permitted sender) client-ip=74.125.83.52; envelope-from=tadas.varanavicius@gmail.com; helo=mail-ee0-f52.google.com; Received: from mail-ee0-f52.google.com ([74.125.83.52]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UFC6h-0003xG-S0 for bitcoin-development@lists.sourceforge.net; Mon, 11 Mar 2013 23:26:17 +0000 Received: by mail-ee0-f52.google.com with SMTP id b15so2305457eek.25 for ; Mon, 11 Mar 2013 16:26:09 -0700 (PDT) X-Received: by 10.14.223.199 with SMTP id v47mr41230177eep.18.1363044369534; Mon, 11 Mar 2013 16:26:09 -0700 (PDT) Received: from [192.168.0.100] ([78.63.237.16]) by mx.google.com with ESMTPS id m46sm26321653eeo.16.2013.03.11.16.26.08 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 11 Mar 2013 16:26:08 -0700 (PDT) Message-ID: <513E680F.6000002@gmail.com> Date: Tue, 12 Mar 2013 01:26:07 +0200 From: =?UTF-8?B?VGFkYXMgVmFyYW5hdmnEjWl1cw==?= 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 References: <20130310043155.GA20020@savin> <75F78378-7580-4D69-A5EA-E943AF7CEB0C@benlabs.net> <513E2BC6.2050102@gmail.com> <513E59EE.7070605@gmail.com> In-Reply-To: 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: 1UFC6h-0003xG-S0 Cc: Bitcoin Dev 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 23:26:18 -0000 On 03/12/2013 12:39 AM, Mike Hearn wrote: > RAM is used as a database cache. > > But regardless, what kind of attack are you thinking of? Using up all > available disk seeks by sending a node a lot of fake transactions that > connect to unspent outputs, but have invalid transactions? You'll get > yourself disconnected and the IP banned even with todays code. I'm thinking that (assuming 2000 tx/s and UTXO growing 50 GB/year) a malicious miner could create 1 GB of unspent outputs and then spam nodes with valid transactions. This would not be dangerous, if UTXO were smaller and fit on RAM. Thank you for reading and correcting me :)