{"type":"rich","version":"1.0","author_name":"npub1tjephawh7fdf6358jufuh5eyxwauzrjqa7qn50pglee4tayc2ntqcjtl6r","author_url":"https://nostr.ae/npub1tjephawh7fdf6358jufuh5eyxwauzrjqa7qn50pglee4tayc2ntqcjtl6r","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-04-10\n📝 Original message:There were earlier discussions.\n\nThe two ideas were either using one or a few service bits to indicate\navailability of blocks, or to extend addr messages with some flags to\nindicate this information.\n\nI wonder whether we can't have a hybrid: bits to indicate general\ndegree of availability of blocks (none, only recent, everything), but\nindicate actual availability only upon actually connecting (through a\n\"version\" extension, or - preferably - a separate message). Reason is\nthat the actual blocks available are likely to change frequently (if\nyou keep the last week of blocks, a 3-day old addr entry will have\nquite outdated information), and not that important to actual peer\nselection - only to drive the decision which blocks to ask after\nconnection.\n\nOn Thu, Apr 10, 2014 at 1:09 PM, Wladimir \u003claanwj at gmail.com\u003e wrote:\n\u003e On Thu, Apr 10, 2014 at 8:04 AM, Tamas Blummer \u003ctamas at bitsofproof.com\u003e\n\u003e wrote:\n\u003e\u003e\n\u003e\u003e Serving headers should be default but storing and serving full blocks\n\u003e\u003e configurable to ranges, so people can tailor to their bandwith and space\n\u003e\u003e available.\n\u003e\n\u003e\n\u003e I do agree that it is important.\n\u003e\n\u003e This does require changes to the P2P protocol, as currently there is no way\n\u003e for a node to signal that they store only part of the block chain. Also,\n\u003e clients will have to be modified to take this into account. Right now they\n\u003e are under the assumption that every full node can send them every (previous)\n\u003e block.\n\u003e\n\u003e What would this involve?\n\u003e\n\u003e Do you know of any previous work towards this?\n\u003e\n\u003e Wladimir\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Put Bad Developers to Shame\n\u003e Dominate Development with Jenkins Continuous Integration\n\u003e Continuously Automate Build, Test \u0026 Deployment\n\u003e Start a new project now. Try Jenkins in the cloud.\n\u003e http://p.sf.net/sfu/13600_Cloudbees\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e"}