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
|
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 <jgarzik@bitpay.com>) id 1V1M0S-0007dA-PN
for bitcoin-development@lists.sourceforge.net;
Mon, 22 Jul 2013 19:42:52 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com
designates 74.125.82.177 as permitted sender)
client-ip=74.125.82.177; envelope-from=jgarzik@bitpay.com;
helo=mail-we0-f177.google.com;
Received: from mail-we0-f177.google.com ([74.125.82.177])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1V1M0R-0005vz-TU
for bitcoin-development@lists.sourceforge.net;
Mon, 22 Jul 2013 19:42:52 +0000
Received: by mail-we0-f177.google.com with SMTP id m19so6335615wev.22
for <bitcoin-development@lists.sourceforge.net>;
Mon, 22 Jul 2013 12:42:45 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:date:message-id:subject:from:to:content-type
:x-gm-message-state;
bh=iq3YhpIYDd4wadHRSOBKfN/CBITIKfZhm/wlLJDouKw=;
b=kzP9b5oTt5iOtMpsGBEYhup5QldFpRug5RO/Q2VHwX/kIJiEC8C6fKekO2J5LdrGeF
1+mTBx6d6vezuEoa/bGkokjGg1OHIqQtWv2g2U+Mopv4uaNwDR+auYjrmEsSU+Use6Lf
JGJGseKuSzkJG6B0t+2ErYWxTgAB2XlkI2iP+0wriK8B3Iol9zIguvgkRDYoVLj6bdD6
kJ0NasAHv4EuAx0r2aqGunVJPAikj4USa9jgMwtMVmtZDDlQQFigRpPovQxlH2oUL9NC
yft5q0chs8KDwKYGqH5XgRmXBneRg65KNFo8gaP5EKLP/oz68Bo05Su3j7KM0HqzrT/b
Pglg==
MIME-Version: 1.0
X-Received: by 10.194.7.137 with SMTP id j9mr20982510wja.11.1374522165740;
Mon, 22 Jul 2013 12:42:45 -0700 (PDT)
Received: by 10.194.242.36 with HTTP; Mon, 22 Jul 2013 12:42:45 -0700 (PDT)
Date: Mon, 22 Jul 2013 15:42:45 -0400
Message-ID: <CAJHLa0Ou1xF=LeLVu_wH1-XgJ1PavDV7_NHoDevo3R9+4z-ZfQ@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQnDsRKz/q90biSeUU1eN3cwB13c0B7vImU0GNWHx1VBhzZZ0lUeXWPhk89wYM+BJ+i4iY+7
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 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: 1V1M0R-0005vz-TU
Subject: [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 19:42:52 -0000
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/
|
