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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <michael@ndrix.org>) id 1V1OXM-000761-Ns
for bitcoin-development@lists.sourceforge.net;
Mon, 22 Jul 2013 22:25:00 +0000
X-ACL-Warn:
Received: from out1-smtp.messagingengine.com ([66.111.4.25])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1V1OX6-0000AD-PO
for bitcoin-development@lists.sourceforge.net;
Mon, 22 Jul 2013 22:25:00 +0000
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45])
by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 8E52021321
for <bitcoin-development@lists.sourceforge.net>;
Mon, 22 Jul 2013 18:06:16 -0400 (EDT)
Received: from frontend2 ([10.202.2.161])
by compute5.internal (MEProxy); Mon, 22 Jul 2013 18:06:17 -0400
X-Sasl-enc: 8cBAh/MTCzAh+k99KrbzEiy/45igFfmQxnkbM24ppCOY 1374530775
Received: from mail-vb0-f45.google.com (unknown [209.85.212.45])
by mail.messagingengine.com (Postfix) with ESMTPA id 910CB68013E
for <bitcoin-development@lists.sourceforge.net>;
Mon, 22 Jul 2013 18:06:15 -0400 (EDT)
Received: by mail-vb0-f45.google.com with SMTP id p14so5011721vbm.32
for <bitcoin-development@lists.sourceforge.net>;
Mon, 22 Jul 2013 15:06:15 -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:date:message-id:subject:from:to
:cc:content-type;
bh=v+q94VYObv6nj9ttfjk0jDBOCU9vvHCfShRtsN0G7os=;
b=Tk8KMQm0j0x1DtzODw/Qi7hA7sXyqc6QgiE+oRNfFrZQoDq9zVuq2d6cVWMLUbt3MH
SW/OT7nWLOAq2X1f1lKVV4hV/ICEas/SEG28YCnIokEt1SxVfuayLezEvYYY8GXJq+Rv
K0MHL6GSS93VkCae+6k27ZTnUPYUev6Z9eA8yoQwcW9SbXRaw/TO2i9hxEFEY9Io/43N
s1+J3hFN4PAgiH5uzJUru8oyMeXETWbfDiaBCCpo1DzM28g2fMq1o/tvoo29A5T/LyCo
HAmZWU+uH8p/I3oA2W8gSKD/5jx2EdSiMsBr8dfNE460aWhz4QKM0IrO1+IPcHzOpkoR
FrxA==
MIME-Version: 1.0
X-Received: by 10.52.26.231 with SMTP id o7mr1876325vdg.105.1374530775363;
Mon, 22 Jul 2013 15:06:15 -0700 (PDT)
Received: by 10.58.8.111 with HTTP; Mon, 22 Jul 2013 15:06:15 -0700 (PDT)
Received: by 10.58.8.111 with HTTP; Mon, 22 Jul 2013 15:06:15 -0700 (PDT)
In-Reply-To: <CAJHLa0Ou1xF=LeLVu_wH1-XgJ1PavDV7_NHoDevo3R9+4z-ZfQ@mail.gmail.com>
References: <CAJHLa0Ou1xF=LeLVu_wH1-XgJ1PavDV7_NHoDevo3R9+4z-ZfQ@mail.gmail.com>
Date: Mon, 22 Jul 2013 16:06:15 -0600
Message-ID: <CAFHuXubk9qZ6ZKjO+xu0+0vHicGSPbPN2Ow=VphGj5b_yXNqjw@mail.gmail.com>
From: Michael Hendricks <michael@ndrix.org>
To: Jeff Garzik <jgarzik@bitpay.com>
Content-Type: multipart/alternative; boundary=20cf3079bdec9940c904e220e23e
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.0 HTML_MESSAGE BODY: HTML included in message
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
0.0 TIME_LIMIT_EXCEEDED Exceeded time limit / deadline
X-Headers-End: 1V1OX6-0000AD-PO
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] HTTP REST API 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: Mon, 22 Jul 2013 22:25:00 -0000
--20cf3079bdec9940c904e220e23e
Content-Type: text/plain; charset=UTF-8
+1 and thank you. I've prototyped a couple different Bitcoin projects that
would benefit from this.
I'm traveling with poor 'net so I haven't read the patches yet. I echo pull
request comments about using Accept and Accept-Encoding headers. Same for
an API version number in the URL.
It'd be helpful, eventually, to have APIs corresponding to Bitcoin addr and
version messages. Metadata about the network and the peer, respectively,
are valuable in my use cases.
Michael
On Jul 22, 2013 1:43 PM, "Jeff Garzik" <jgarzik@bitpay.com> wrote:
> URL: https://github.com/bitcoin/bitcoin/pull/2844
>
> Adding an HTTP REST API for bitcoind has been occasionally tossed
> about as a useful thing. Such an API would essentially provide a
> decentralized block explorer capability, enabling easy external access
> to transaction/address/block indices that we maintain.
>
> The first two implemented API calls are simple, returning a block or
> TX given a simple query string based on block hash, e.g.
>
> GET /rest/tx/TX-HASH
> or
> GET /rest/block/BLOCK-HASH
>
> This can be easily accessed via command line cURL/wget utilities.
> Output formats -- binary, hex or json -- may be selected via a
> "bitcoin-format" header.
>
> The general goal of the HTTP REST interface is to access
> unauthenticated, public blockchain information. There is no plan to
> add wallet interfacing/manipulation via this API.
>
> --
> Jeff Garzik
> Senior Software Engineer and open source evangelist
> BitPay, Inc. https://bitpay.com/
>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--20cf3079bdec9940c904e220e23e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<p dir=3D"ltr">+1 and thank you. I've prototyped a couple different Bit=
coin projects that would benefit from this.</p>
<p dir=3D"ltr">I'm traveling with poor 'net so I haven't read t=
he patches yet. I echo pull request comments about using Accept and Accept-=
Encoding headers. Same for an API version number in the URL.</p>
<p dir=3D"ltr">It'd be helpful, eventually, to have APIs corresponding =
to Bitcoin addr and version messages.=C2=A0 Metadata about the network and =
the peer, respectively, are valuable in my use cases.</p>
<p dir=3D"ltr">Michael</p>
<div class=3D"gmail_quote">On Jul 22, 2013 1:43 PM, "Jeff Garzik"=
<<a href=3D"mailto:jgarzik@bitpay.com">jgarzik@bitpay.com</a>> wrote=
:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
URL: <a href=3D"https://github.com/bitcoin/bitcoin/pull/2844" target=3D"_bl=
ank">https://github.com/bitcoin/bitcoin/pull/2844</a><br>
<br>
Adding an HTTP REST API for bitcoind has been occasionally tossed<br>
about as a useful thing. =C2=A0Such an API would essentially provide a<br>
decentralized block explorer capability, enabling easy external access<br>
to transaction/address/block indices that we maintain.<br>
<br>
The first two implemented API calls are simple, returning a block or<br>
TX given a simple query string based on block hash, e.g.<br>
<br>
=C2=A0 =C2=A0 =C2=A0GET /rest/tx/TX-HASH<br>
or<br>
=C2=A0 =C2=A0 =C2=A0GET /rest/block/BLOCK-HASH<br>
<br>
This can be easily accessed via command line cURL/wget utilities.<br>
Output formats -- binary, hex or json -- may be selected via a<br>
"bitcoin-format" header.<br>
<br>
The general goal of the HTTP REST interface is to access<br>
unauthenticated, public blockchain information. =C2=A0There is no plan to<b=
r>
add wallet interfacing/manipulation via this API.<br>
<br>
--<br>
Jeff Garzik<br>
Senior Software Engineer and open source evangelist<br>
BitPay, Inc. =C2=A0 =C2=A0 =C2=A0<a href=3D"https://bitpay.com/" target=3D"=
_blank">https://bitpay.com/</a><br>
<br>
---------------------------------------------------------------------------=
---<br>
See everything from the browser to the database with AppDynamics<br>
Get end-to-end visibility with application monitoring from AppDynamics<br>
Isolate bottlenecks and diagnose root cause in seconds.<br>
Start your free trial of AppDynamics Pro today!<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D48808831&iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D48808831&iu=3D/4140/ostg.clktrk</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div>
--20cf3079bdec9940c904e220e23e--
|
