From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WXFEb-0000ae-1d for bitcoin-development@lists.sourceforge.net; Mon, 07 Apr 2014 19:29:33 +0000 Received: from mail-pa0-f42.google.com ([209.85.220.42]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WXFEZ-0000aN-SD for bitcoin-development@lists.sourceforge.net; Mon, 07 Apr 2014 19:29:33 +0000 Received: by mail-pa0-f42.google.com with SMTP id fb1so7273357pad.1 for ; Mon, 07 Apr 2014 12:29:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:organization:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=sd3YUR4Ms9hrZEXlXc6fKiITMyfJgecc2NbKwyaUXkw=; b=KmT+08wb4trxa4AI1X9JXB34DTZb3XsjGhtI0QvLV6yPrvsidkavnikmW/T3nMYGG/ 7gwvPYSo3rikMKC/zQbJZjt/3QQquaEl6IqsipvPAi6Md8sSas1xsQDpmsANA7DOCL2i dBOF5agAwYMq32AZ67M8yUd/XA3boY9MGlzyzQh1uXh36lcQ9+mdSnM/6GiNOQby6HA+ FJe49H1Pwzmd/L2ty7wp4HUhglurOzn44gFegn/lldpIZnSp8kukgEMYjkA6kXXwLxUV x6J58zdIKOdW4sg7y73sAelPrUExEsH2yl7qlPZQ8W6vO8ei5Vv4j8mLDWgvjzWlMnew HkGg== X-Gm-Message-State: ALoCoQkjMslkNpF6n+RVoHmxFtRyWrAnv/q2+aYCWo4t+m5AgDUjWFsebvBZKWTaU5RJXxBWvOwW X-Received: by 10.68.139.137 with SMTP id qy9mr32762214pbb.11.1396898965894; Mon, 07 Apr 2014 12:29:25 -0700 (PDT) Received: from [192.168.127.194] (50-0-36-93.dsl.dynamic.sonic.net. [50.0.36.93]) by mx.google.com with ESMTPSA id de5sm31399189pbc.66.2014.04.07.12.29.23 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 07 Apr 2014 12:29:24 -0700 (PDT) Message-ID: <5342F8C0.60500@monetize.io> Date: Mon, 07 Apr 2014 12:13:04 -0700 From: Mark Friedenbach Organization: Monetize.io Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net 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> In-Reply-To: <8222EAFD-813E-4046-A751-FD3D04FF6764@bitsofproof.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1WXFEZ-0000aN-SD 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 19:29:33 -0000 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!