summaryrefslogtreecommitdiff
path: root/d5/525481cdda028054fdea11e966e6cf632b1d6d
blob: 08c74685ded796fc290b8284d57b026d502470c6 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <peter@coinlab.com>) id 1SfBeL-0007OR-Nh
	for bitcoin-development@lists.sourceforge.net;
	Thu, 14 Jun 2012 15:07:53 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of coinlab.com
	designates 209.85.213.175 as permitted sender)
	client-ip=209.85.213.175; envelope-from=peter@coinlab.com;
	helo=mail-yx0-f175.google.com; 
Received: from mail-yx0-f175.google.com ([209.85.213.175])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
	(Exim 4.76) id 1SfBeL-0000gS-5x
	for bitcoin-development@lists.sourceforge.net;
	Thu, 14 Jun 2012 15:07:53 +0000
Received: by yenl13 with SMTP id l13so1589361yen.34
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 14 Jun 2012 08:07:47 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type:x-gm-message-state;
	bh=5sE3nk/20cPqk/O/y4O7qS71ztdle0SyKrPtDLIORZI=;
	b=Yj7rhkzcAFj+PoJMxLjrsmVp4lkuY5gkBqo+LVyAuvVlUn7GjQisHujmbKhGX9V3dd
	nluM1gqC4s6u9we8r0LA5Cb+WJBSNI93m1z4Ha5w/aUZtHWVJ9uxqtmem4cheFQsM6Ib
	OOxqt56ZiQ1fgdh3suQhMobh1CBNFy5dMijIJanG9CWayoihDGrgFnLkC4gP5T14xbYv
	eT76JNyF8HOQGO1FbGeqr8kfaY+x6km1NOM/+NIw7WHD4IALzxdxT+YfJIxq0XSMDRPs
	7M1lSsstUXWXcbBtlulJyPRewAiYsVfeh2X3Td9dE2apoVLn/C4zu8+evVEHDyMPal1l
	bTFQ==
Received: by 10.60.171.101 with SMTP id at5mr2011802oec.73.1339684667151; Thu,
	14 Jun 2012 07:37:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.41.200 with HTTP; Thu, 14 Jun 2012 07:37:26 -0700 (PDT)
In-Reply-To: <CABsx9T0oZvVB1CPfa7Rk3CTnPOx8-CEm4K45pjACSyoqLz6YPA@mail.gmail.com>
References: <CABsx9T0oZvVB1CPfa7Rk3CTnPOx8-CEm4K45pjACSyoqLz6YPA@mail.gmail.com>
From: Peter Vessenes <peter@coinlab.com>
Date: Thu, 14 Jun 2012 10:37:26 -0400
Message-ID: <CAMGNxUvYiOqr=4rTOPwC6pCa1MmxWcVAqMk62=85mLiAntgfwA@mail.gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec54a3692b256d504c26fa4d3
X-Gm-Message-State: ALoCoQmJPBD/qIlrYQk5pJUV5kuPI0vabcNI72BBDF5KR2h04kpEhOMg08HgzoTEJ3+5+efjYmfF
X-Spam-Score: -0.5 (/)
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 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
X-Headers-End: 1SfBeL-0000gS-5x
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 14 Jun 2012 15:07:53 -0000

--bcaec54a3692b256d504c26fa4d3
Content-Type: text/plain; charset=ISO-8859-1

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.

Peter


On Thu, Jun 14, 2012 at 9:22 AM, Gavin Andresen <gavinandresen@gmail.com>wrote:

> I submitted a pull request yesterday that implements low-level "raw"
> transaction, and am looking for feedback on the API and help with
> trying to test/break it.
> ...

--bcaec54a3692b256d504c26fa4d3
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

This is super cool!=A0<div><br></div><div>I have a feature request: it woul=
d be awesome to be able to provide private keys at the command line with th=
e signature, turning the client into a wallet-less signature machine.</div>

<div><br></div><div>Peter</div><div><br><br><div class=3D"gmail_quote">On T=
hu, Jun 14, 2012 at 9:22 AM, Gavin Andresen <span dir=3D"ltr">&lt;<a href=
=3D"mailto:gavinandresen@gmail.com" target=3D"_blank">gavinandresen@gmail.c=
om</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I submitted a pull request yesterday that im=
plements low-level &quot;raw&quot;<br>
transaction, and am looking for feedback on the API and help with<br>
trying to test/break it.<br>...</blockquote></div>
</div>

--bcaec54a3692b256d504c26fa4d3--