Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1SfGE8-0000nV-Hh for bitcoin-development@lists.sourceforge.net; Thu, 14 Jun 2012 20:01:08 +0000 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; Received: from mail-ey0-f175.google.com ([209.85.215.175]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1SfGE4-0002yu-Rw for bitcoin-development@lists.sourceforge.net; Thu, 14 Jun 2012 20:01:08 +0000 Received: by eaal1 with SMTP id l1so730601eaa.34 for ; Thu, 14 Jun 2012 13:00:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.14.99.206 with SMTP id x54mr834379eef.94.1339704058292; Thu, 14 Jun 2012 13:00:58 -0700 (PDT) Received: by 10.14.3.66 with HTTP; Thu, 14 Jun 2012 13:00:57 -0700 (PDT) In-Reply-To: References: Date: Thu, 14 Jun 2012 16:00:57 -0400 Message-ID: From: Gavin Andresen To: Peter Vessenes Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gavinandresen[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1SfGE4-0002yu-Rw Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Raw Transaction RPC calls for bitcoind 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: Thu, 14 Jun 2012 20:01:08 -0000 On Thu, Jun 14, 2012 at 10:37 AM, Peter Vessenes 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