From: Gavin Andresen <gavinandresen@gmail•com>
To: Peter Vessenes <peter@coinlab•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Raw Transaction RPC calls for bitcoind
Date: Thu, 14 Jun 2012 16:00:57 -0400 [thread overview]
Message-ID: <CABsx9T1BUzn0ZBvWrEsrX_6BZ1LWCUdXqFsrO_vhfEfVUz=VHA@mail.gmail.com> (raw)
In-Reply-To: <CAMGNxUvYiOqr=4rTOPwC6pCa1MmxWcVAqMk62=85mLiAntgfwA@mail.gmail.com>
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
prev parent reply other threads:[~2012-06-14 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 13:22 Gavin Andresen
2012-06-14 14:37 ` Peter Vessenes
2012-06-14 20:00 ` Gavin Andresen [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='CABsx9T1BUzn0ZBvWrEsrX_6BZ1LWCUdXqFsrO_vhfEfVUz=VHA@mail.gmail.com' \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=peter@coinlab$(echo .)com \
/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