Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WXHNB-0007Re-Ge for bitcoin-development@lists.sourceforge.net; Mon, 07 Apr 2014 21:46:33 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.179 as permitted sender) client-ip=74.125.82.179; envelope-from=ricardojdfilipe@gmail.com; helo=mail-we0-f179.google.com; Received: from mail-we0-f179.google.com ([74.125.82.179]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WXHNA-0001hr-Gh for bitcoin-development@lists.sourceforge.net; Mon, 07 Apr 2014 21:46:33 +0000 Received: by mail-we0-f179.google.com with SMTP id x48so56795wes.10 for ; Mon, 07 Apr 2014 14:46:26 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.110.100 with SMTP id hz4mr45335611wjb.50.1396907186211; Mon, 07 Apr 2014 14:46:26 -0700 (PDT) Received: by 10.217.128.207 with HTTP; Mon, 7 Apr 2014 14:46:26 -0700 (PDT) In-Reply-To: <5342F8C0.60500@monetize.io> 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> <5342F8C0.60500@monetize.io> Date: Mon, 7 Apr 2014 22:46:26 +0100 Message-ID: From: Ricardo Filipe To: Mark Friedenbach Content-Type: text/plain; charset=ISO-8859-1 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 (ricardojdfilipe[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: 1WXHNA-0001hr-Gh Cc: Bitcoin Dev 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:46:33 -0000 Or have blocks distributed through pruned nodes as a DHT. 2014-04-07 20:13 GMT+01:00 Mark Friedenbach : > > > On 04/07/2014 12:20 PM, Tamas Blummer wrote: >> Validation has to be sequantial, but that step can be deferred until the >> blocks before a point are loaded and continous. > > And how do you find those blocks? > > I have a suggestion: have nodes advertise which range of full blocks > they possess, then you can perform synchronization from the adversed ranges! > > ------------------------------------------------------------------------------ > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment > Start a new project now. Try Jenkins in the cloud. > http://p.sf.net/sfu/13600_Cloudbees > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development