From: "Wladimir J. van der Laan" <laanwj@gmail•com>
To: xor@freenetproject•org
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin Core 0.12.0 release candidate 1 available
Date: Mon, 18 Jan 2016 12:14:16 +0100 [thread overview]
Message-ID: <20160118111416.GA23240@amethyst.visucore.com> (raw)
In-Reply-To: <2974102.cQI6F9PQvI@1337h4x0r>
On Sun, Jan 17, 2016 at 11:57:28PM +0100, xor--- via bitcoin-dev wrote:
> On Sunday, January 17, 2016 11:08:08 AM Wladimir J. van der Laan via bitcoin-
> dev wrote:
> > Preliminary release notes for the release can be found here:
> >
> > https://github.com/bitcoin/bitcoin/blob/0.12/doc/release-notes.md
>
>
> The part which lists raw Git pull requests says:
> > #6057 ac5476e re-enable wallet in autoprune
>
> But the main, handwritten part does not mention this.
> Is pruning really finished, i.e. could I safely use it as a wallet "end-user"?
It has been tested in git for almost half a year. This RC is the first binary
release that contains the functionality.
It is extremely unlikely that the wallet will eat your coins (always backup
nevertheless), but I can't guarantee there won't be some issue where the wallet
and chain get out of sync and you're forced to redownload the blockchain.
> IMHO it would be one of the most interesting feature for users, as it could
> fix the issue of taking >60 GB of disk space.
>
> So if it is finished, please mention that
> - it's finished
> - how to enable it.
How to enable it is still the same as mentioned in the 0.11 release notes:
https://github.com/bitcoin/bitcoin/blob/v0.11.0/doc/release-notes.md#block-file-pruning
Wladimir
next prev parent reply other threads:[~2016-01-18 11:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 10:08 Wladimir J. van der Laan
2016-01-17 22:57 ` xor
2016-01-18 11:14 ` Wladimir J. van der Laan [this message]
2016-01-19 6:06 ` xor
2016-01-25 12:03 ` Wladimir J. van der Laan
2016-01-25 12:27 ` xor
2016-01-25 14:44 ` Marco Falke
2016-01-25 15:05 ` Wladimir J. van der Laan
2016-01-25 15:57 ` Simon Selitsky
2016-01-25 16:12 ` Jonas Schnelli
2016-01-25 17:33 ` xor
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=20160118111416.GA23240@amethyst.visucore.com \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=xor@freenetproject$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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