From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WYDOL-0006Dn-PQ for bitcoin-development@lists.sourceforge.net; Thu, 10 Apr 2014 11:43:37 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of petertodd.org designates 62.13.149.115 as permitted sender) client-ip=62.13.149.115; envelope-from=pete@petertodd.org; helo=outmail149115.authsmtp.co.uk; Received: from outmail149115.authsmtp.co.uk ([62.13.149.115]) by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1WYDOK-0003S6-QR for bitcoin-development@lists.sourceforge.net; Thu, 10 Apr 2014 11:43:37 +0000 Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235]) by punt18.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s3ABhTYo093580; Thu, 10 Apr 2014 12:43:29 +0100 (BST) Received: from [25.121.248.92] ([24.114.49.14]) (authenticated bits=0) by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s3ABhPlC021818 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Apr 2014 12:43:27 +0100 (BST) User-Agent: K-9 Mail for Android In-Reply-To: References: <534570A2.9090502@gmx.de> <0B038624-8861-438E-B7B1-566B4A8E126B@bitsofproof.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 From: Peter Todd Date: Thu, 10 Apr 2014 07:43:21 -0400 To: Pieter Wuille , Wladimir Message-ID: <9b2cddd4-0c46-422e-ac34-0598d47b6a75@email.android.com> X-Server-Quench: 55200cf8-c0a5-11e3-b802-002590a15da7 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR aQdMdwIUGUUGAgsB AmIbWlZeVF57W2s7 aQ5PbARZfE5HQQRu T0xPR01TWkZrcG5Z ZkJtUhtzfwRONn9y YUZiEHVeXkR6JhB1 Xx1URGgbZGY1a31N WEBaagNUcgZDfk5E bwQuUz1vNG8XDQg5 AwQ0PjZ0MThBJSBS WgQAK04nCWwKAjU7 RhYOWDQpWEcMTCY8 NRs7LFJUGUEdPw08 NkFpYmomUgAbDglT A1ol X-Authentic-SMTP: 61633532353630.1023:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 24.114.49.14/465 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. 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 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1WYDOK-0003S6-QR Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Bitcoind-in-background mode for SPV wallets 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: Thu, 10 Apr 2014 11:43:37 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 10 April 2014 07:32:44 GMT-04:00, Pieter Wuille wrote: >There were earlier discussions. > >The two ideas were either using one or a few service bits to indicate >availability of blocks, or to extend addr messages with some flags to >indicate this information. > >I wonder whether we can't have a hybrid: bits to indicate general >degree of availability of blocks (none, only recent, everything), but >indicate actual availability only upon actually connecting (through a >"version" extension, or - preferably - a separate message). Reason is >that the actual blocks available are likely to change frequently (if >you keep the last week of blocks, a 3-day old addr entry will have >quite outdated information), and not that important to actual peer >selection - only to drive the decision which blocks to ask after >connection. Why not just put an expiration date on that information and delay deletion until the expiration is reached? Also, its worth noting how the node bit solution you proposed can be done as a gradual upgrade path for SPV client. From the perspective of nodes that don't know about it they just see the pruned nodes as SPV nodes without any chain data at all. The only issue would be if large numbers of uses turned off their full nodes, but that's a possibility regardless. Done with partial UTXO set mode this may even result in an eventual increase in the number of full nodes. -----BEGIN PGP SIGNATURE----- Version: APG v1.1.1 iQFQBAEBCgA6BQJTRoPZMxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8 cGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhetrCACA02EJQ0VpcYvafuNc 7pvqMVeirJRu3Uv7Wy8rcl9jW5irM5fmNdznARtv2vwpEZN7MU0wp3ZY1FYOCv2f PvWC7DBCSBs2BuyGkvPuwnXEppTrYmWFT3qjg+99lF1IlOV4yWFacja2RGDuJkea fYUkODosHJjFVcXi5aMkBPQ5sOFdlUVbC94YV4d4PDSmF2fHLGG8uEfEweYb6Pv+ gj1CsfuAWf8DWzygDeL8x/wOG9HeqYqEbjxyOb9hxlp1ByUof+4WJtz3QfGsR2Xt fvkmgS8vkUxSIZorMdypj7oLBOnfDW1bEK5He2SlqPdYi5FEQusZ/jMMX3Fw74GV fJKt =Wyv8 -----END PGP SIGNATURE-----