From: Wladimir <laanwj@gmail•com>
To: Gavin Andresen <gavinandresen@gmail•com>
Cc: Bitcoin-Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] minor bitcoin-qt gripes moving BTC off specific key
Date: Tue, 7 May 2013 15:14:08 +0200 [thread overview]
Message-ID: <CA+s+GJBbRwueBvaXcYMgM0b_LeChbDcBA0HQHQP9CvjnXzXhLg@mail.gmail.com> (raw)
In-Reply-To: <CABsx9T10Gdzt_7RQK-Jv9fc6GEesj8nmxkGy=f_5j-Np09958Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1585 bytes --]
On Tue, May 7, 2013 at 2:28 PM, Gavin Andresen <gavinandresen@gmail•com>wrote:
> "sweep private key" is the missing functionality.
>
> I agree, it would be nice to have.
>
>
> On Tue, May 7, 2013 at 8:16 AM, Adam Back <adam@cypherspace•org> wrote:
>
>> Hi
>>
>> Three minor security/other issues:
>>
>> 1. please a way to unlock the wallet without displaying wallet password in
>> console screen (console unlock wallet, to import priv key); or
>>
>> 2. a button to import a private key (and option to transfer it to another
>> key - if you are not the sole controller the private key)
>>
>> 3. a UX way to transfer BTC off a specific adress (eg choose from
>> address), rather than having to spend the entire wallet onto a new
>> address, just to get BTC off a specific address. Doing it that way has
>> problems: creates more network traffic/bigger packets, higher fees (if
>> any transactions are young/low confirmation), and generally damages
>> privacy as all your funds end up linked.
>>
>
Yes, sweep (send all the coins from this addresses to me) should certainly
be added. Maybe even a way to do it periodically, though but that would
require remembering the key.
Importing private keys into the wallet will not be added as a user-friendly
option, as it is dangerous and potentially confusing.
As for (1), I think a better solution would to add a list of commands whose
arguments are censored in the console screen and command line history. At
least `importprivkey`, `walletpassphrase`, `walletpassphrasechange` should
likely be in that list.
Wladimir
[-- Attachment #2: Type: text/html, Size: 2547 bytes --]
next prev parent reply other threads:[~2013-05-07 13:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 12:16 Adam Back
2013-05-07 12:28 ` Gavin Andresen
2013-05-07 13:14 ` Wladimir [this message]
2013-05-07 13:19 ` Pieter Wuille
2013-05-07 16:06 ` Adam Back
2013-05-07 16:44 ` Craig B Agricola
2013-05-10 15:27 ` Jesus Cea
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=CA+s+GJBbRwueBvaXcYMgM0b_LeChbDcBA0HQHQP9CvjnXzXhLg@mail.gmail.com \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gavinandresen@gmail$(echo .)com \
/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