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
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1SfA0F-0001Wk-4q
for bitcoin-development@lists.sourceforge.net;
Thu, 14 Jun 2012 13:22:23 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.83.47 as permitted sender)
client-ip=74.125.83.47; envelope-from=gavinandresen@gmail.com;
helo=mail-ee0-f47.google.com;
Received: from mail-ee0-f47.google.com ([74.125.83.47])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1SfA07-0000xG-DB
for bitcoin-development@lists.sourceforge.net;
Thu, 14 Jun 2012 13:22:23 +0000
Received: by eekd49 with SMTP id d49so588398eek.34
for <bitcoin-development@lists.sourceforge.net>;
Thu, 14 Jun 2012 06:22:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.14.22.69 with SMTP id s45mr539716ees.186.1339680128965; Thu,
14 Jun 2012 06:22:08 -0700 (PDT)
Received: by 10.14.3.66 with HTTP; Thu, 14 Jun 2012 06:22:08 -0700 (PDT)
Date: Thu, 14 Jun 2012 09:22:08 -0400
Message-ID: <CABsx9T0oZvVB1CPfa7Rk3CTnPOx8-CEm4K45pjACSyoqLz6YPA@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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: 1SfA07-0000xG-DB
Subject: [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 13:22:23 -0000
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.
Design doc: https://gist.github.com/2839617
Pull request: https://github.com/bitcoin/bitcoin/pull/1456
Test plan: https://secure.bettermeans.com/projects/4180/wiki/Raw_Transactio=
n_RPC_Test_Plan
Playing around with this API on the command line I'm pretty happy with
the level of abstraction and the way it interacts with existing RPC
commands; for example, "createrawtx" is just like "sendmany" in the
way outputs are specified.
The signrawtx method is the key new method; it takes a raw
transaction, signs as many inputs as it can, and returns the same raw
transaction with signatures. Typical usage would be:
Funds are sitting in a multisignature transaction output, and it is
time to gather signatures and spend them.
Assumption: you know the multisignature transaction's [txid,
outputNumber, amount].
Create a raw transaction to spend, using createrawtx.
Use signrawtx to add your signatures (after unlocking the wallet, if necess=
ary).
Give the transaction to the other person(s) to sign.
You or they submit the transaction to the network using sendrawtx.
I don't imagine anybody but very-early-adopters or ultra-geeks will do
this by calling these RPC methods at a command-line. They are really
intended for people writing services on top of bitcoind. The service
should be careful to include an appropriate transaction fee, or the
sendrawtx method is likely to fail.
I've been asked a couple of times: why doesn't signrawtx handle the
BIP 0010 (https://en.bitcoin.it/wiki/BIP_0010) transaction format?
I considered parsing/writing BIP 10 format for raw transactions, but
decided that reading/writing BIP 10 format should happen at a higher
level and not in the low-level RPC calls. So 'raw transactions' are
simply hex-encoded into JSON strings, and encoding/decoding them is
just a couple of lines of already-written-and-debugged code.
------
Here is the help output and example use for all the new RPC calls:
listunspent [minconf=3D1] [maxconf=3D999999]
Returns array of unspent transaction outputs
with between minconf and maxconf (inclusive) confirmations.
Returns an array of 4-element arrays, each of which is:
[transaction id, output, amount, confirmations]
E.g: listunspent 1 2
Returns:
[
[
"2881b33a8c0bbdb45b0a65b36aa6611a05201e316ea3ad718762d48ef9588fb3",
0,
40.00000000,
2
],
[
"894a0fc535c7b49f434ceb633d8555ea24c8f9775144efb42da85b853280bcd7",
0,
50.00000000,
1
]
]
getrawtx <txid>
Returns hexadecimal-encoded, serialized transaction data
for <txid>. Returns an error if <txid> is unknown.
E.g.: getrawtx fce46ea2448820f7bb8091b5f5e3fd75b7b267e60b9a22af88a9eeabfb08=
4233
Returns:
01000000016d40da062b6a0edcaf643b6e25b943baf103941589d287e39d6f425d84ae8b1c0=
00000004847304402203fb648ff8381d8961e66ef61ab88afe52826a5179b8a7312742c8d93=
785ca56302204240ea12de1211fffab49686f13ca0e78011d1985765be6e6aa8e747852f897=
d01ffffffff0100f2052a0100000017a914f96e358e80e8b3660256b211a23ce3377d2f9cb1=
8700000000
createrawtx [["txid",n],...] {address:amount,...}
Create a transaction spending given inputs
(array of (hex transaction id, output number) pairs),
sending to given address(es).
Returns the same information as gettransaction, plus an
extra "rawtx" key with the hex-encoded transaction.
Note that the transaction's inputs are not signed, and
it is not stored in the wallet or transmitted to the network.
E.g.: createrawtx '[
["fce46ea2448820f7bb8091b5f5e3fd75b7b267e60b9a22af88a9eeabfb084233",0]
]' '{"mqYmZSQQuAWNQcdwBrDwmtTXg2TLNz748L":50}'
Returns:
{
"version" : 1,
"locktime" : 0,
"size" : 85,
"vin" : [
{
"prevout" : {
"hash" :
"fce46ea2448820f7bb8091b5f5e3fd75b7b267e60b9a22af88a9eeabfb084233",
"n" : 0
},
"scriptSig" : "",
"sequence" : 4294967295
}
],
"vout" : [
{
"value" : 50.00000000,
"scriptPubKey" : "OP_DUP OP_HASH160
6e0920fc26383dc7e6101bc417cf87169d0cedbd OP_EQUALVERIFY OP_CHECKSIG"
}
],
"rawtx" : "0100000001334208fbabeea988af229a0be667b2b775fde3f5b59180bbf7=
208844a26ee4fc0000000000ffffffff0100f2052a010000001976a9146e0920fc26383dc7e=
6101bc417cf87169d0cedbd88ac00000000"
}
signrawtx <hex string> [<prevtx1>,<prevtx2>...]
Sign inputs for raw transaction (serialized, hex-encoded).
Second argument is an array of raw previous transactions that
this transaction depends on but are not yet in the blockchain.
Returns json object with keys:
rawtx : raw transaction with signature(s) (hex-encoded string)
complete : 1 if transaction has a complete set of signature (0 if not)
E.g.: signrawtx
"0100000001334208fbabeea988af229a0be667b2b775fde3f5b59180bbf7208844a26ee4fc=
0000000000ffffffff0100f2052a010000001976a9146e0920fc26383dc7e6101bc417cf871=
69d0cedbd88ac00000000"
'["01000000016d40da062b6a0edcaf643b6e25b943baf103941589d287e39d6f425d84ae8b=
1c000000004847304402203fb648ff8381d8961e66ef61ab88afe52826a5179b8a7312742c8=
d93785ca56302204240ea12de1211fffab49686f13ca0e78011d1985765be6e6aa8e747852f=
897d01ffffffff0100f2052a0100000017a914f96e358e80e8b3660256b211a23ce3377d2f9=
cb18700000000"]'
Returns:
{
"rawtx" : "0100000001334208fbabeea988af229a0be667b2b775fde3f5b59180bbf7=
208844a26ee4fc000000009100473044022007f3ba1b8bdc156f2340ef1222eb287c3f5481a=
8078a8dad43aa09fd289ba19002201cc72e97406d546dc918159978dc78aee8215a64183759=
56665ee44e6eacc1150147522102894ca6e7a6483d0f8fa6110c77c431035e8d462e3a93225=
5d9dda65e8fada55c2103c556ef01e89a07ee9ba61581658fa007bf442232daed8b465c47c2=
78550d3dab52aeffffffff0100f2052a010000001976a9146e0920fc26383dc7e6101bc417c=
f87169d0cedbd88ac00000000",
"complete" : false
}
sendrawtx <hex string>
Submits raw transaction (serialized, hex-encoded) to local node and network=
.
E.g.: sendrawtx
0100000001334208fbabeea988af229a0be667b2b775fde3f5b59180bbf7208844a26ee4fc0=
00000009100473044022007f3ba1b8bdc156f2340ef1222eb287c3f5481a8078a8dad43aa09=
fd289ba19002201cc72e97406d546dc918159978dc78aee8215a6418375956665ee44e6eacc=
1150147522102894ca6e7a6483d0f8fa6110c77c431035e8d462e3a932255d9dda65e8fada5=
5c2103c556ef01e89a07ee9ba61581658fa007bf442232daed8b465c47c278550d3dab52aef=
fffffff0100f2052a010000001976a9146e0920fc26383dc7e6101bc417cf87169d0cedbd88=
ac00000000
Returns:
error: {"code":-22,"message":"TX rejected"}
(Rejected because it doesn't have all required signatures, if it was
accepted it would return the transaction id)
--=20
--
Gavin Andresen
|
