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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <runesvend@gmail.com>) id 1V8Fog-0004OV-SC
for bitcoin-development@lists.sourceforge.net;
Sat, 10 Aug 2013 20:31:14 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.170 as permitted sender)
client-ip=74.125.82.170; envelope-from=runesvend@gmail.com;
helo=mail-we0-f170.google.com;
Received: from mail-we0-f170.google.com ([74.125.82.170])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1V8Fof-0001Gj-1H
for bitcoin-development@lists.sourceforge.net;
Sat, 10 Aug 2013 20:31:14 +0000
Received: by mail-we0-f170.google.com with SMTP id w60so4514404wes.15
for <bitcoin-development@lists.sourceforge.net>;
Sat, 10 Aug 2013 13:31:06 -0700 (PDT)
X-Received: by 10.180.187.235 with SMTP id fv11mr3087365wic.65.1376166666769;
Sat, 10 Aug 2013 13:31:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.95.8 with HTTP; Sat, 10 Aug 2013 13:30:46 -0700 (PDT)
In-Reply-To: <51EEDB57.4070108@monetize.io>
References: <CAJHLa0Ou1xF=LeLVu_wH1-XgJ1PavDV7_NHoDevo3R9+4z-ZfQ@mail.gmail.com>
<201307231030.14139.andyparkins@gmail.com>
<20130723094703.GA25900@savin>
<ksllu7$9i$1@ger.gmane.org> <51EEDB57.4070108@monetize.io>
From: =?ISO-8859-1?Q?Rune_Kj=E6r_Svendsen?= <runesvend@gmail.com>
Date: Sat, 10 Aug 2013 22:30:46 +0200
Message-ID: <CAH2=CKz2epe2rJFPDN5FdqNK8X58CCMaHLVHPgK23tNmq6cRwg@mail.gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a11c25aa0531bc404e39dc5a8
X-Spam-Score: -0.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
(runesvend[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1V8Fof-0001Gj-1H
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: Sat, 10 Aug 2013 20:31:15 -0000
--001a11c25aa0531bc404e39dc5a8
Content-Type: text/plain; charset=ISO-8859-1
I think this is a useful feature, but I din't see why it should be a part
of bitcoind. I've created a simple HTTP REST wrapper around bitcoind's RPC
interface in Python:
https://github.com/runeksvendsen/btchttp/blob/master/btchttp.py
It simply runs a HTTP server that translates HTTP GET requests into the
relevant RPC request, and responds to the GET request with the relevant
data.
/Rune
On Tue, Jul 23, 2013 at 9:36 PM, Mark Friedenbach <mark@monetize.io> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> On 7/23/13 3:29 AM, Andreas Schildbach wrote:
> >
> > Yes, I understand that. For this reason, I would vote for adding the
> > usual HTTP authentication/SSL stuff to the REST API. That way, SPV users
> > can decide to run their own instance of the API (providing the needed
> > resources themselves).
> >
> > Or, a trusted party can set up a server. For example, I would be willing
> > to set it up for users of Bitcoin Wallet. I don't expect shitloads of
> > paper wallets sweeps for the forseeable future.
> >
> >
> Anyone who wants HTTP authentication or TLS can wrap it with nginx, or
> something similar. In the process they could put appropriate
> restrictions in place on incoming requests, and the onus would be on
> them, not us to keep it secure.
>
> Mark
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBAgAGBQJR7ttWAAoJEAdzVfsmodw4UmIP/36lK2TDc7mLTT8rbflJhl3v
> TL4CFKhXj6OuzG7tyino3Djs4EQnyk+CbpfOmJ8kYr29GPaZttuDJhYXtJqQBQCi
> DPq79ktudHnVMLPirEs7dUrLo+TAqhYX+8Sj+eTlW+p6YZg3JbkOAIPJG7597OK4
> zzU8Oxr0XKJFfGscKfkPThxJboNqzJYGl3otHUMXM4HsbIRYmrx4QSr8y7dsVgTd
> YZnD4bJO+eY4ZPzCcFdkPD/8bXQyKC5nPOH8/79lARNLESwB4OW79uf9q86EuH2O
> jZQ1qwpRNHblrNWS1/U2E4+7hEidvgZBwQhj+HbWgKiPWh4Df1lEXq6bLQQwdn6/
> b+jfiwg7xpb7eB2M4gPZ0uF/1TIcGJN3+LWEULFNTT/vsjyD/UU63ahZ1kVv7X0m
> W1NrbKjXxDbip+x3N7HLIu3zqAAaa0ele7OysyFCL6ZlwwafwJiEZZgHn2Iw7I1L
> S7lYBbFoLfXlOMVXNaKHPEV5gQEveMROJVBtnWkqShPQM0N/+Z+TXZes37up0GVo
> d7ptPfNbUNDTFc8Jj3+5rIyy3dUvSyMJlHZhsLmtCUnbQ867ZOgeUS52a8XQ+nJY
> 8IsShLfLk6fRWmHrwo9lzZQ/TbbUNyoUje0Ns6iL7G3IZwDqJH3kAGb/bkj/piDu
> tPNcN8bkYeNobTFIH+o4
> =jV80
> -----END PGP SIGNATURE-----
>
>
>
> ------------------------------------------------------------------------------
> 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
>
--001a11c25aa0531bc404e39dc5a8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">I think this is a useful feature, but I din't see why =
it should be a part of bitcoind. I've created a simple HTTP REST wrappe=
r around bitcoind's RPC interface in Python:=A0<a href=3D"https://githu=
b.com/runeksvendsen/btchttp/blob/master/btchttp.py" target=3D"_blank">https=
://github.com/runeksvendsen/btchttp/blob/master/btchttp.py</a><div>
<br></div><div>It simply runs a HTTP server that translates HTTP GET reques=
ts into the relevant RPC request, and responds to the GET request with the =
relevant data.</div><div class=3D"gmail_extra"><br clear=3D"all"><div>
<div>/Rune</div></div><div><br></div><div class=3D"gmail_quote">On Tue, Jul=
23, 2013 at 9:36 PM, Mark Friedenbach <span dir=3D"ltr"><<a href=3D"mai=
lto:mark@monetize.io" target=3D"_blank">mark@monetize.io</a>></span> wro=
te:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<div><br>
<br>
On 7/23/13 3:29 AM, Andreas Schildbach wrote:<br>
><br>
> Yes, I understand that. For this reason, I would vote for adding the<b=
r>
> usual HTTP authentication/SSL stuff to the REST API. That way, SPV use=
rs<br>
> can decide to run their own instance of the API (providing the needed<=
br>
> resources themselves).<br>
><br>
> Or, a trusted party can set up a server. For example, I would be willi=
ng<br>
> to set it up for users of Bitcoin Wallet. I don't expect shitloads=
of<br>
> paper wallets sweeps for the forseeable future.<br>
><br>
><br>
</div>Anyone who wants HTTP authentication or TLS can wrap it with nginx, o=
r<br>
something similar. In the process they could put appropriate<br>
restrictions in place on incoming requests, and the onus would be on<br>
them, not us to keep it secure.<br>
<br>
Mark<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)<br>
Comment: GPGTools - <a href=3D"http://gpgtools.org" target=3D"_blank">http:=
//gpgtools.org</a><br>
Comment: Using GnuPG with Thunderbird - <a href=3D"http://www.enigmail.net/=
" target=3D"_blank">http://www.enigmail.net/</a><br>
<br>
iQIcBAEBAgAGBQJR7ttWAAoJEAdzVfsmodw4UmIP/36lK2TDc7mLTT8rbflJhl3v<br>
TL4CFKhXj6OuzG7tyino3Djs4EQnyk+CbpfOmJ8kYr29GPaZttuDJhYXtJqQBQCi<br>
DPq79ktudHnVMLPirEs7dUrLo+TAqhYX+8Sj+eTlW+p6YZg3JbkOAIPJG7597OK4<br>
zzU8Oxr0XKJFfGscKfkPThxJboNqzJYGl3otHUMXM4HsbIRYmrx4QSr8y7dsVgTd<br>
YZnD4bJO+eY4ZPzCcFdkPD/8bXQyKC5nPOH8/79lARNLESwB4OW79uf9q86EuH2O<br>
jZQ1qwpRNHblrNWS1/U2E4+7hEidvgZBwQhj+HbWgKiPWh4Df1lEXq6bLQQwdn6/<br>
b+jfiwg7xpb7eB2M4gPZ0uF/1TIcGJN3+LWEULFNTT/vsjyD/UU63ahZ1kVv7X0m<br>
W1NrbKjXxDbip+x3N7HLIu3zqAAaa0ele7OysyFCL6ZlwwafwJiEZZgHn2Iw7I1L<br>
S7lYBbFoLfXlOMVXNaKHPEV5gQEveMROJVBtnWkqShPQM0N/+Z+TXZes37up0GVo<br>
d7ptPfNbUNDTFc8Jj3+5rIyy3dUvSyMJlHZhsLmtCUnbQ867ZOgeUS52a8XQ+nJY<br>
8IsShLfLk6fRWmHrwo9lzZQ/TbbUNyoUje0Ns6iL7G3IZwDqJH3kAGb/bkj/piDu<br>
tPNcN8bkYeNobTFIH+o4<br>
=3DjV80<br>
-----END PGP SIGNATURE-----<br>
<div><div><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" target=3D"_bla=
nk">Bitcoin-development@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>
</div></div></blockquote></div><br></div></div>
--001a11c25aa0531bc404e39dc5a8--
|
