<oembed><type>rich</type><version>1.0</version><author_name>npub1dktdyz5xuuzugc00zyjr46zdqca2grcks4qyj0qz6ulms78ml2vqchk0xl</author_name><author_url>https://nostr.ae/npub1dktdyz5xuuzugc00zyjr46zdqca2grcks4qyj0qz6ulms78ml2vqchk0xl</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2017-08-16&#xA;📝 Original message:I read about prune option right now, actually i didn&#39;t hear about it before.&#xA;Yes this option can save some disk space but afaik first (awful N-days&#xA;lasting) synchronization still requires to download full database.&#xA;My approach also cuts database and replaces all old blocks (except say last&#xA;6 blocks for security reason)&#xA;with series of blocks with rolled initial totals and optionally purged from&#xA;tiny wallets crap (storing on six thousand current nodes and on the swarm&#xA;of full wallets&#xA; information that John have 100 satosi is too expensive for us and we may&#xA;annually clear that balance as fee for miners or just delete).&#xA;&#xA;So almost all nodes can hold only the rolled database (i can&#39;t estimate&#xA;compression ration of the rolled database now, i am not advanced user as&#xA;you can see).&#xA; And only much less amount of archive nodes holds full expanded database.&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;2017-08-16 19:52 GMT+03:00 Nick ODell &lt;nickodell at gmail.com&gt;:&#xA;&#xA;&gt; What makes this approach better than the prune option of Bitcoin?&#xA;&gt;&#xA;&gt; On Wed, Aug 16, 2017 at 10:20 AM, Алексей Мутовкин via bitcoin-dev &lt;&#xA;&gt; bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&gt;&#xA;&gt;&gt;&#xA;&gt;&gt; Let me describe the possible improvement of the bitcoin blockchain&#xA;&gt;&gt; database (BBD)  size in general terms.&#xA;&gt;&gt;&#xA;&gt;&gt; We can implement new routine : annual split of the BBD. Reason is that&#xA;&gt;&gt; 140gb full wallet unconvinience.&#xA;&gt;&gt;&#xA;&gt;&gt; BBD splits in two parts :&#xA;&gt;&gt; 1) old blocks before the date of split and&#xA;&gt;&gt; 2) new blocks, starting from first technical block with all rolled totals&#xA;&gt;&gt; on the date of split.&#xA;&gt;&gt;     (also possible transfer of tiny totals due to their unprofitability&#xA;&gt;&gt; to the miners, so we cut long tail of tiny holders)&#xA;&gt;&gt; 3) old blocks packs into annual megablocks and stores in the side archive&#xA;&gt;&gt; chain for some needs for FBI investigations or other goals.&#xA;&gt;&gt;&#xA;&gt;&gt;&#xA;&gt;&gt; Thanks for your attention,&#xA;&gt;&gt;&#xA;&gt;&gt; Alexey Mutovkin&#xA;&gt;&gt;&#xA;&gt;&gt;&#xA;&gt;&gt;&#xA;&gt;&gt;&#xA;&gt;&gt;&#xA;&gt;&gt;&#xA;&gt;&gt;&#xA;&gt;&gt;&#xA;&gt;&gt;&#xA;&gt;&gt;&#xA;&gt;&gt;&#xA;&gt;&gt;&#xA;&gt;&gt;&#xA;&gt;&gt; _______________________________________________&#xA;&gt;&gt; bitcoin-dev mailing list&#xA;&gt;&gt; bitcoin-dev at lists.linuxfoundation.org&#xA;&gt;&gt; https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev&#xA;&gt;&gt;&#xA;&gt;&gt;&#xA;&gt;&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170816/b3e2dc85/attachment.html&gt;</html></oembed>