Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UFBNM-0000jb-EB for bitcoin-development@lists.sourceforge.net; Mon, 11 Mar 2013 22:39:24 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.174 as permitted sender) client-ip=209.85.214.174; envelope-from=mh.in.england@gmail.com; helo=mail-ob0-f174.google.com; Received: from mail-ob0-f174.google.com ([209.85.214.174]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UFBNL-0000nw-7I for bitcoin-development@lists.sourceforge.net; Mon, 11 Mar 2013 22:39:24 +0000 Received: by mail-ob0-f174.google.com with SMTP id 16so3896067obc.33 for ; Mon, 11 Mar 2013 15:39:17 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.60.22.69 with SMTP id b5mr10827901oef.38.1363041557883; Mon, 11 Mar 2013 15:39:17 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.86.169 with HTTP; Mon, 11 Mar 2013 15:39:17 -0700 (PDT) In-Reply-To: <513E59EE.7070605@gmail.com> References: <20130310043155.GA20020@savin> <75F78378-7580-4D69-A5EA-E943AF7CEB0C@benlabs.net> <513E2BC6.2050102@gmail.com> <513E59EE.7070605@gmail.com> Date: Mon, 11 Mar 2013 23:39:17 +0100 X-Google-Sender-Auth: M6-C-Z_ZjI1abDYaH7s6mNT_CwM Message-ID: From: Mike Hearn To: =?UTF-8?Q?Tadas_Varanavi=C4=8Dius?= Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 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: 1UFBNL-0000nw-7I 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 22:39:24 -0000 > Isn't there danger of an attack if UTXO is not stored in fast storage? 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. It's much easier to hose a node by just asking it to send you the block chain. Watch your own node when something is syncing the chain from it. Ping times go through the roof because there's only one network thread. If you're worried about DoS attacks on Bitcoin, it'd be better to fix that first.