public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Pieter Wuille <pieter.wuille@gmail.com>
To: Adam Back <adam@cypherspace.org>
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:19:50 +0200	[thread overview]
Message-ID: <20130507131948.GA4231@vps7135.xlshosting.net> (raw)
In-Reply-To: <20130507121641.GA11770@netbook.cypherspace.org>

On Tue, May 07, 2013 at 02:16:41PM +0200, Adam Back 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 

I think the general solution here is providing a feature-reach Python RPC client,
which can do things like remember passwords, command history/tab completion,
perhaps even batch lookups of compound commands (getblock $(getblockhash X, for
example, ...). The naive RPC client built into bitcoind is not a good fit for
many features, as they can much more efficiently be developed outside of the
core binary,


> 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)

I'm quite opposed to any per-key fiddling in the GUI. This will inevitably lead
to (even more) people misunderstanding how wallets work and shooting themself in
the foot. I don't mind an expert mode ("coin control") that enables such features,
but in general, we should for entire-wallet export and import rather than
individual keys.

Import & sweep an address is something else, that sounds safe to.

> 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.

This belongs in coin control, IMHO.

-- 
Pieter




  parent reply	other threads:[~2013-05-07 13:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-07 12:16 [Bitcoin-development] minor bitcoin-qt gripes moving BTC off specific key Adam Back
2013-05-07 12:28 ` Gavin Andresen
2013-05-07 13:14   ` Wladimir
2013-05-07 13:19 ` Pieter Wuille [this message]
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=20130507131948.GA4231@vps7135.xlshosting.net \
    --to=pieter.wuille@gmail.com \
    --cc=adam@cypherspace.org \
    --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