{"type":"rich","version":"1.0","author_name":"npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2p","author_url":"https://nostr.ae/npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2p","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-04-10\n📝 Original message:On Thu, Apr 10, 2014 at 8:04 AM, Tamas Blummer \u003ctamas at bitsofproof.com\u003ewrote:\n\n\u003e Serving headers should be default but storing and serving full blocks\n\u003e configurable to ranges, so people can tailor to their bandwith and space\n\u003e available.\n\u003e\n\nI do agree that it is important.\n\nThis does require changes to the P2P protocol, as currently there is no way\nfor a node to signal that they store only part of the block chain. Also,\nclients will have to be modified to take this into account. Right now they\nare under the assumption that every full node can send them every\n(previous) block.\n\nWhat would this involve?\n\nDo you know of any previous work towards this?\n\nWladimir\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140410/fb3a77bb/attachment.html\u003e"}