Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.215.175 as permitted sender)
	client-ip=209.85.215.175; envelope-from=gavinandresen@gmail.com;
	helo=mail-ey0-f175.google.com; 
MIME-Version: 1.0
In-Reply-To: <CAMGNxUvYiOqr=4rTOPwC6pCa1MmxWcVAqMk62=85mLiAntgfwA@mail.gmail.com>
References: <CABsx9T0oZvVB1CPfa7Rk3CTnPOx8-CEm4K45pjACSyoqLz6YPA@mail.gmail.com>
	<CAMGNxUvYiOqr=4rTOPwC6pCa1MmxWcVAqMk62=85mLiAntgfwA@mail.gmail.com>
Date: Thu, 14 Jun 2012 16:00:57 -0400
Message-ID: <CABsx9T1BUzn0ZBvWrEsrX_6BZ1LWCUdXqFsrO_vhfEfVUz=VHA@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Peter Vessenes <peter@coinlab.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Raw Transaction RPC calls for bitcoind
Precedence: list

On Thu, Jun 14, 2012 at 10:37 AM, Peter Vessenes <peter@coinlab.com> wrote:
> This is super cool!
>
> I have a feature request: it would be awesome to be able to provide private
> keys at the command line with the signature, turning the client into a
> wallet-less signature machine.

I like that idea.

A third argument that is an array of private keys (in the same format
as the dumpprivkey RPC call) should be easy to support, assuming the
semantics are:

+ If third argument given, do not require that the wallet be unlocked,
and only sign using the private key(s) given (ignore the bitcoind
wallet entirely).
+ Private keys would stay in bitcoind memory only for the duration of
the RPC call.

-- 
--
Gavin Andresen