Re: [bitcoin-dev] Fwd: Proposal of a new BIP : annual splitting blockchain database to reduce its size.

2017-08-16 Thread Luke Dashjr via bitcoin-dev
To have a BIP, you need to explain not only *why* you want to do something, but also *what specifically* to do, and *how* to do it. This concept (historically known as "flip the chain" and/or "UTXO commitments") is not new, merely complicated to design and implement. Luke On Wednesday 16 Augu

Re: [bitcoin-dev] Fwd: Proposal of a new BIP : annual splitting blockchain database to reduce its size.

2017-08-16 Thread Алексей Мутовкин via bitcoin-dev
I read about prune option right now, actually i didn't hear about it before. Yes this option can save some disk space but afaik first (awful N-days lasting) synchronization still requires to download full database. My approach also cuts database and replaces all old blocks (except say last 6 blocks

Re: [bitcoin-dev] Fwd: Proposal of a new BIP : annual splitting blockchain database to reduce its size.

2017-08-16 Thread Nick ODell via bitcoin-dev
What makes this approach better than the prune option of Bitcoin? On Wed, Aug 16, 2017 at 10:20 AM, Алексей Мутовкин via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > > Let me describe the possible improvement of the bitcoin blockchain > database (BBD) size in general terms. > >

[bitcoin-dev] Fwd: Proposal of a new BIP : annual splitting blockchain database to reduce its size.

2017-08-16 Thread Алексей Мутовкин via bitcoin-dev
Let me describe the possible improvement of the bitcoin blockchain database (BBD) size in general terms. We can implement new routine : annual split of the BBD. Reason is that 140gb full wallet unconvinience. BBD splits in two parts : 1) old blocks before the date of split and 2) new blocks, sta