public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tadas Varanavicius <tadas.varanavicius@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Release candidates: versions 0.4.1 and 0.5
Date: Thu, 17 Nov 2011 01:25:39 +0200	[thread overview]
Message-ID: <4EC44673.4080101@gmail.com> (raw)
In-Reply-To: <CABsx9T2QUTzvC3cWOnc6Gc-EyCT-6hX4NO=-7yogzohRC+fn4w@mail.gmail.com>

Hello,

newbie here, thanks for patience.

I start 0.5.0 without wallet.dat. It creates 100 new keys. I then 
encrypt them. It should be now bug free and totally secure, so I back 
the wallet up. I then click "new address", it doesn't use the old 2-100 
addresses, instead generates a new batch, because it assumes the old 
ones are leaked, but in fact they are not. I receive funds to my new 2nd 
address (which is now not backed up). I lose the new wallet. Restore 
from backup. Bitcoins lost forever?

Sorry if false alarm, thanks.

On 11/16/2011 06:34 PM, Gavin Andresen wrote:
> I need help sanity testing these:
>    https://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.4.1/test/
>    https://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.0/test/
>
-- 
Tadas Varanavičius
+37061529855




  reply	other threads:[~2011-11-16 23:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-16 16:34 [Bitcoin-development] Release candidates: versions 0.4.1 and 0.5 Gavin Andresen
2011-11-16 23:25 ` Tadas Varanavicius [this message]
2011-11-17 15:33 ` Martinx - ジェームズ
2011-11-17 15:35   ` Martinx - ジェームズ
2011-11-17 16:26 ` Martinx - ジェームズ
2011-11-17 18:43   ` Martinx - ジェームズ
2011-11-17 20:16   ` Michael Hendricks
     [not found] ` <4EC56CF2.1070704@parhelic.com>
2011-11-17 20:24   ` Jordan Mack

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=4EC44673.4080101@gmail.com \
    --to=tadas.varanavicius@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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