MIME-Version: 1.0
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
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] HTTP REST API for bitcoind
Precedence: list

--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&#39;ve prototyped a couple different Bit=
coin projects that would benefit from this.</p>
<p dir=3D"ltr">I&#39;m traveling with poor &#39;net so I haven&#39;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&#39;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, &quot;Jeff Garzik&quot;=
 &lt;<a href=3D"mailto:jgarzik@bitpay.com">jgarzik@bitpay.com</a>&gt; 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>
&quot;bitcoin-format&quot; 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&amp;iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D48808831&amp;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--