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-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WXHWn-0008Es-CX for bitcoin-development@lists.sourceforge.net; Mon, 07 Apr 2014 21:56:29 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.217.175 as permitted sender) client-ip=209.85.217.175; envelope-from=gmaxwell@gmail.com; helo=mail-lb0-f175.google.com; Received: from mail-lb0-f175.google.com ([209.85.217.175]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WXHWm-0004LV-MO for bitcoin-development@lists.sourceforge.net; Mon, 07 Apr 2014 21:56:29 +0000 Received: by mail-lb0-f175.google.com with SMTP id w7so54545lbi.20 for ; Mon, 07 Apr 2014 14:56:22 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.153.7.69 with SMTP id da5mr3221006lad.38.1396907781966; Mon, 07 Apr 2014 14:56:21 -0700 (PDT) Received: by 10.112.89.68 with HTTP; Mon, 7 Apr 2014 14:56:21 -0700 (PDT) In-Reply-To: References: <5342C833.5030906@gmail.com> <6D430188-CE00-44B1-BD8C-B623CF04D466@icloudtools.net> <6D6E55CE-2F04-4C34-BEE6-98AEF1478346@bitsofproof.com> <8A6DEBA4-EA59-4BAE-95CF-C964C2DBB84B@bitsofproof.com> <8222EAFD-813E-4046-A751-FD3D04FF6764@bitsofproof.com> Date: Mon, 7 Apr 2014 14:56:21 -0700 Message-ID: From: Gregory Maxwell To: Tier Nolan Content-Type: text/plain; charset=UTF-8 X-Spam-Score: 1.1 (+) 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 (gmaxwell[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 1.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net [Blocked - see ] 1.5 SF_NO_SPF_SPAM SF_NO_SPF_SPAM X-Headers-End: 1WXHWm-0004LV-MO Cc: Bitcoin Development Subject: Re: [Bitcoin-development] Why are we bleeding nodes? 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, 07 Apr 2014 21:56:29 -0000 On Mon, Apr 7, 2014 at 2:48 PM, Tier Nolan wrote: >> Blocks can be loaded in random order once you have their order given by >> the headers. >> Computing the UTXO however will force you to at least temporarily store >> the blocks unless you have plenty of RAM. > You only need to store the UTXO set, rather than the entire block chain. The comment was specifically in the context of an out of order fetch. Verification must be in order. If you have fetched blocks out of order you must preserve them at least long enough to reorder them. Thats all.