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
|
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 <laanwj@gmail.com>) id 1Xif36-0005IF-BE
for bitcoin-development@lists.sourceforge.net;
Mon, 27 Oct 2014 07:49:08 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.177 as permitted sender)
client-ip=209.85.213.177; envelope-from=laanwj@gmail.com;
helo=mail-ig0-f177.google.com;
Received: from mail-ig0-f177.google.com ([209.85.213.177])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Xif35-0005hP-I1
for bitcoin-development@lists.sourceforge.net;
Mon, 27 Oct 2014 07:49:08 +0000
Received: by mail-ig0-f177.google.com with SMTP id h18so2684049igc.4
for <bitcoin-development@lists.sourceforge.net>;
Mon, 27 Oct 2014 00:49:02 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.43.148.74 with SMTP id kf10mr17952711icc.9.1414396142259;
Mon, 27 Oct 2014 00:49:02 -0700 (PDT)
Received: by 10.64.249.170 with HTTP; Mon, 27 Oct 2014 00:49:02 -0700 (PDT)
In-Reply-To: <CAKaEYhJfY+zhnzWBa76u+=o1jAsxG-+j5c6RYDS+nhSDi1QDQQ@mail.gmail.com>
References: <CA+s+GJA3-qK71TcUCYQ3xOdi+zgE_fB9N6NJkNBUDtWnA-0dcA@mail.gmail.com>
<CAKaEYhJfY+zhnzWBa76u+=o1jAsxG-+j5c6RYDS+nhSDi1QDQQ@mail.gmail.com>
Date: Mon, 27 Oct 2014 08:49:02 +0100
Message-ID: <CA+s+GJDqRBFpGS-8rsjodiCscD_swG9mZ=R0EQO+rVi_ed=Kcw@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Melvin Carvalho <melvincarvalho@gmail.com>
Content-Type: text/plain; charset=UTF-8
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
(laanwj[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: 1Xif35-0005hP-I1
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin Core 0.10 release schedule
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, 27 Oct 2014 07:49:08 -0000
On Sun, Oct 26, 2014 at 12:44 PM, Melvin Carvalho
<melvincarvalho@gmail.com> wrote:
> Firstly, apologies in coming in late to the conversation. As I am also
> working on a REST API for electronic coins. Some questions:
>
> 1. Is there a BIP, or some other doc (e.g. gist), outlining the REST output
> e.g. the response format and MIME types. Or just compile from source?
See the opening post from @jgarzik, it has some documentation on how
to use the API.
It would be nice to have some write-up about the current functionality
in the release notes, but there currently is none.
It's a RPC-side change, not a P2P-side change so it doesn't require a BIP.
> 2. How set in stone is v1 of the the going forward? PS I support @maaku's
> comments re: "/api/v1/" -- tho I guess it is too late for that now.
> 3. Would there be any support to develop this interface into something that
> would be W3C standards compliant, or reviewed by the REST community. So for
> example a context can be provided to self document the terms (something I've
> almost completed) and would allow standardization of block explorer and
> bitcoind outputs. Right now every explorer seems to have a different JSON
> output.
It's not too late, it's not been merged yet.
Though a W3C standard takes a long time to pan out, and it may be more
useful to have this available rather than wait for the API to be
standardized (which means this will need to be postponed at least one
version). As you say, a new interface be added later under another
URI.
Note that we're only interested in exposing read-only, public data
which is already available in Bitcoin Core's internals.
We're not aiming to add a fully-fledged block explorer with (say)
address indexes. Although that could be part of the standard if it
allows implementations to support just a subset.
Anyhow - please coordinate this with Jeff Garzik, it's better to work
together here.
Wladimir
|
