From: Jesus Cea <jcea@jcea•es>
To: Bitcoin-Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] minor bitcoin-qt gripes moving BTC off specific key
Date: Fri, 10 May 2013 17:27:34 +0200 [thread overview]
Message-ID: <518D11E6.3000204@jcea.es> (raw)
In-Reply-To: <20130507121641.GA11770@netbook.cypherspace.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/05/13 14:16, Adam Back wrote:
> 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.
[...]
> Then I wanted to take the .01 BTC off the private key and the FAQs
> etc seem to suggest that the only way to do it is to spend our
> entire balance (from all keys) onto a new address. Not exactly
> what I wanted, but I did it anyway and the tx fee goes up from
> .0001 which I set it to to .0005 because the transaction was young,
> to avoid network flooding. Even though transaction I actually
> wanted to move (on the non self-controlled key had a big heap of
> confirmations and so could've been .0001 tx fee).
"sendfrom" in the RPC interface. Difficult to use (I would like to be
able to use source key, in addition of source "accounts") and easy to
make mistakes. But doable.
Would be nice to have an "advanced" GUI option to chooce source
account/key.
- --
Jesús Cea Avión _/_/ _/_/_/ _/_/_/
jcea@jcea•es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/
Twitter: @jcea _/_/ _/_/ _/_/_/_/_/
jabber / xmpp:jcea@jabber•org _/_/ _/_/ _/_/ _/_/ _/_/
"Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/
"My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQCVAwUBUY0R5plgi5GaxT1NAQLJ6AQAkWozxNWJdMYbIBKFTxsPErmv3LChAsYm
bzVIb8ufwV45X0QT3maxz6A/u3yr4wGxu53Vs29dJkM5rgO5JU7akuPs3qvg3ffh
h593zmqyVimfpXxBppff4vocpKTCJ+1ocB5MydGjgGoH2hJ8dwZNQRHYnMwqCjDf
2ONQu7nT0pQ=
=zZVh
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2013-05-10 15:27 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
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 [this message]
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=518D11E6.3000204@jcea.es \
--to=jcea@jcea$(echo .)es \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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