From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-dev@lists.linuxfoundation.org,
"Алексей Мутовкин" <alex.mutovkin@gmail.com>
Subject: Re: [bitcoin-dev] Fwd: Proposal of a new BIP : annual splitting blockchain database to reduce its size.
Date: Wed, 16 Aug 2017 18:33:47 +0000 [thread overview]
Message-ID: <201708161833.48897.luke@dashjr.org> (raw)
In-Reply-To: <CAEadUT+oty3vU0LOMMoOdy7yNF92q+rgGbtV-AgjO8PGknZ+gg@mail.gmail.com>
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 August 2017 4:20:45 PM Алексей Мутовкин via bitcoin-dev wrote:
> 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, starting from first technical block with all rolled totals
> on the date of split.
> (also possible transfer of tiny totals due to their unprofitability to
> the miners, so we cut long tail of tiny holders)
> 3) old blocks packs into annual megablocks and stores in the side archive
> chain for some needs for FBI investigations or other goals.
>
>
> Thanks for your attention,
>
> Alexey Mutovkin
prev parent reply other threads:[~2017-08-16 18:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEadUTKo12vscHQUpjA16kQkrKBp34iw-JTRf0TdwUc9rqzznQ@mail.gmail.com>
2017-08-16 16:20 ` [bitcoin-dev] Fwd: Proposal of a new BIP : annual splitting blockchain database to reduce its size Алексей Мутовкин
2017-08-16 16:52 ` Nick ODell
2017-08-16 17:37 ` Алексей Мутовкин
2017-08-16 18:33 ` Luke Dashjr [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201708161833.48897.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=alex.mutovkin@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox