public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: xor@freenetproject.org
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin Core 0.12.0 release candidate 1 available
Date: Tue, 19 Jan 2016 07:06:50 +0100	[thread overview]
Message-ID: <1591452.8UA7xN1qih@1337h4x0r> (raw)
In-Reply-To: <20160118111416.GA23240@amethyst.visucore.com>

[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]

On Monday, January 18, 2016 12:14:16 PM Wladimir J. van der Laan wrote:
> 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.

I think I asked the wrong way, sorry: My question was not really meant at 
whether it is bug-free (testing that is the purpose of a release candidate, so 
we of course don't know yet), but rather whether it is at least feature 
complete now.

Remember, the previous v0.11.0 release notes said:
> Block pruning is currently incompatible with running a wallet due to the
> fact that block data is used for rescanning the wallet and importing keys
> or addresses (which require a rescan.) However, running the wallet with
> block pruning will be supported in the near future, subject to those
> limitations.

So I'm interested whether this limitation has been lifted, and the whole 
feature is considered as finished.

If yes, I would highly recommend advertising it in the new release notes - as 
said, the disk space reduction is a big deal.


Thank you!

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2016-01-19  6:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-17 10:08 [bitcoin-dev] Bitcoin Core 0.12.0 release candidate 1 available Wladimir J. van der Laan
2016-01-17 22:57 ` xor
2016-01-18 11:14   ` Wladimir J. van der Laan
2016-01-19  6:06     ` xor [this message]
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=1591452.8UA7xN1qih@1337h4x0r \
    --to=xor@freenetproject.org \
    --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