From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UapEW-0003Zi-5f for bitcoin-development@lists.sourceforge.net; Fri, 10 May 2013 15:27:44 +0000 X-ACL-Warn: Received: from babylon5.jcea.es ([94.23.84.75] helo=smtp.jcea.es) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1UapEU-00032T-C0 for bitcoin-development@lists.sourceforge.net; Fri, 10 May 2013 15:27:44 +0000 Received: from [10.8.0.6] (ks27448.kimsufi.com [91.121.85.130]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.jcea.es (Postfix) with ESMTPSA id 3b6Zzq12MdzXX for ; Fri, 10 May 2013 17:27:35 +0200 (CEST) Message-ID: <518D11E6.3000204@jcea.es> Date: Fri, 10 May 2013 17:27:34 +0200 From: Jesus Cea User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: Bitcoin-Dev References: <20130507121641.GA11770@netbook.cypherspace.org> In-Reply-To: <20130507121641.GA11770@netbook.cypherspace.org> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-15 X-Spam-Probability-jcea: Ham (0.0%) rz: False [3d7f0e93db84cbb7edff98ad8d0d81eb] (None) Content-Transfer-Encoding: quoted-printable X-Spam-Score: -1.3 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.3 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1UapEU-00032T-C0 Subject: Re: [Bitcoin-development] minor bitcoin-qt gripes moving BTC off specific key X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 May 2013 15:27:44 -0000 -----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=20 > address), rather than having to spend the entire wallet onto a new=20 > 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. - --=20 Jes=FAs Cea Avi=F3n _/_/ _/_/_/ _/_/_= / 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=3D =3DzZVh -----END PGP SIGNATURE-----