<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Once a single transaction in pruned in a block, the block is no longer eligible to be served to other nodes. </div><div>Which transactions are pruned can be rather custom e.g. even depending on the wallet(s) of the node,</div><div>therefore I guess it is more handy to return some bitmap of pruned/full blocks than ranges.</div><div><br></div><div apple-content-edited="true"><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; orphans: 2; widows: 2; float: none; display: inline !important;">Tamas Blummer</span><br style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; orphans: 2; widows: 2;"><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; orphans: 2; widows: 2; float: none; display: inline !important;"><a href="http://bitsofproof.com">http://bitsofproof.com</a></span>
</span></div>
<br><div><div>On 07.04.2014, at 20:49, Gregory Maxwell <<a href="mailto:gmaxwell@gmail.com">gmaxwell@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On Mon, Apr 7, 2014 at 11:35 AM, Tamas Blummer <<a href="mailto:tamas@bitsofproof.com">tamas@bitsofproof.com</a>> wrote:<br><blockquote type="cite">BTW, did we already agree on the service bits for an archive node?<br></blockquote><br>I'm still very concerned that a binary archive bit will cause extreme<br>load hot-spotting and the kind of binary "Use lots of resources YES or<br>NO" I think we're currently suffering some from, but at that point<br>enshrined in the protocol.<br><br>It would be much better to extend the addr messages so that nodes can<br>indicate a range or two of blocks that they're serving, so that all<br>nodes can contribute fractionally according to their means. E.g. if<br>you want to offer up 8 GB of distributed storage and contribute to the<br>availability of the blockchain, without having to swollow the whole<br>20, 30, 40 ... gigabyte pill.<br><br>Already we need that kind of distributed storage for the most recent<br>blocks to prevent extreme bandwidth load on archives, so extending it<br>to arbitrary ranges is only more complicated because there is<br>currently no room to signal it.<br><br></blockquote></div><br></body></html>