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 1WXDKD-0006UN-5P for bitcoin-development@lists.sourceforge.net; Mon, 07 Apr 2014 17:27:13 +0000 Received: from mail-pb0-f49.google.com ([209.85.160.49]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WXDKC-0000mI-33 for bitcoin-development@lists.sourceforge.net; Mon, 07 Apr 2014 17:27:13 +0000 Received: by mail-pb0-f49.google.com with SMTP id jt11so7021796pbb.36 for ; Mon, 07 Apr 2014 10:27:06 -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:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=qaiT+a+SWsLbF5Z6d2HAdeefZ/QWXH17eyNh4L7NXkU=; b=fQYkpYaGJ8Ix9rYiq5DwS1Ku2DwQpV7+KEoOX77qPM29OjYHZ/Xb+fSlPJBj4PZdsc 3Ju01w1mj9V33kuGkfTYQxgPk9gX84Zxi3s/+dAzQNSJaFxFD73J6mHYxYBAoq4TiJXo 6eDXUAJPkJLNeWh7FynSkMTy2GYgrFU8JJtQ155DiR/2i98Aa/W5yswvxeEM8glhQjlN RbRbUHYkDkMl2oy6zX6H8hkP7l0TECgmGDS35Ro/jLvlIG4QjWg7t/K+rLh7WuZ3kaGQ tiHZPoKEl2GqWLHgz9G6E0kEof/BXbXcxE9llM8lXi9wie4BckrqzLzKpEuPQEsTCEqi +TFA== X-Gm-Message-State: ALoCoQnWUB6zmhE+ZCCYrbGNIhgZ/9t7NZIdn+Ijj3PDOOB3XXTZFs0dJAAkXvcelOIbf5rT4ock X-Received: by 10.67.15.42 with SMTP id fl10mr1119267pad.30.1396890113337; Mon, 07 Apr 2014 10:01:53 -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 xk3sm37942498pbb.65.2014.04.07.10.01.47 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 07 Apr 2014 10:01:52 -0700 (PDT) Message-ID: <5342D9FA.8080102@monetize.io> Date: Mon, 07 Apr 2014 10:01:46 -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: Gregory Maxwell References: <5342C833.5030906@gmail.com> <5342D1DB.8060203@monetize.io> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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: 1WXDKC-0000mI-33 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 17:27:13 -0000 On 04/07/2014 09:57 AM, Gregory Maxwell wrote: > That is an implementation issue— mostly one that arises as an indirect > consequence of not having headers first and the parallel fetch, not a > requirements issue. Oh, absolutely. But the question "why are people not running full nodes?" has to do with the current implementation, not abstract capabilities of a future version of the bitcoind code base.