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
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
|
Return-Path: <shekharhiran@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 0917D9F0
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 29 Aug 2018 16:06:56 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-it0-f42.google.com (mail-it0-f42.google.com
[209.85.214.42])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5A026796
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 29 Aug 2018 16:06:55 +0000 (UTC)
Received: by mail-it0-f42.google.com with SMTP id h1-v6so5920539itj.4
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 29 Aug 2018 09:06:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to
:cc; bh=ryPAv+tG605le0dqCfLI51ofVKzqAaFpA7+mdFA5c+4=;
b=MbxmJ5LDHNILpCdgHYA0rZZGoJjeGMgXI8SaCH+K2ybhmLjfmO0rzvareqttkUiPDq
hn5KQJ2vQgtYU8dhtXZrkHlmPi9xI3xW2VcVMWS958hA7+E46umb7BqCdgJ5ZXsBiaTR
sBJQuUFrEoKjp2PUQOqTtVVqHMyd5d51ekEqHx+2TxEMp71HUtsgQSbtmjWASRZK1Zow
Hizpdy5wxi3PQQ68Z73K2FKWWunN1mfMpB7Uyfw2hhlUujD33lqtFgMQKyELm7dC8H2O
Qr5TYfpSOYoHXLPHL6/ehQuj4mcRhlH4iSVNZW6Epiqf5hf6qP09O+BVMsJRApVfucp6
O/1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to:cc;
bh=ryPAv+tG605le0dqCfLI51ofVKzqAaFpA7+mdFA5c+4=;
b=lZVX9ocwTNTDq+rrLoM9n34rn523t7SXPmudMRB+G+RrkS8NaJ77CJ/snk3Jz+5stZ
XsOGDOP4vPLpBFGHfejF9+if9ChbPQI+ptHW5/oSbhGeSuJSEEPYdEgbzHSEap3YLhal
42/8vYF38VKI2ja/vwXwgiDbw5iJ81pKmbVAWwIiIa8Tiddd2EDB4ChLZn+F46T8tl0I
+WZlvejW0+NB+3hpSlTBKwCWzNWrDTom5q1ZkteoYZ2ztxTo0reLwnm39RGPG/aZVuWy
FLBuAtNxGvPgRRcyDNwSUrxi/Meg8UtrKucI84IHND71jG7tkAJbkKLk7w/Pk6kjOf+g
ryUQ==
X-Gm-Message-State: APzg51CvKNm3AezqVOLAZ8NgH33LExw+3+jsJshpvdIwV88DaXBwuq2y
rJFB3gEyQUPZ83uHYc6wyV/PAutqrHGKFwc93M5LwmU5
X-Google-Smtp-Source: ANB0VdZeTgGFBrAAGnrUhqdRvIdGdu6a9pATZZYSMTrqldYzbfINThaNniPmPYKdsCda2aZIGfiDhtxnuuZC9DH8GOc=
X-Received: by 2002:a02:85a3:: with SMTP id
d32-v6mr5751005jai.119.1535558814440;
Wed, 29 Aug 2018 09:06:54 -0700 (PDT)
MIME-Version: 1.0
References: <CA+9w0-77oP3rmW37R6ty4fF_LhaOtQaL52yQUKynXEmZhQ9MeA@mail.gmail.com>
<8AE1517F-88FB-479D-AE89-993A5545D210@jonasschnelli.ch>
<758E3CA7-295B-4B77-BFF5-9AAE959D53EA@voskuil.org>
In-Reply-To: <758E3CA7-295B-4B77-BFF5-9AAE959D53EA@voskuil.org>
From: Blockchain Group <shekharhiran@gmail.com>
Date: Wed, 29 Aug 2018 21:36:43 +0530
Message-ID: <CA+9w0-73LzutZaFEQVnb=f_vSh8K8QfULh8Qc6j3x9JpnNBZHg@mail.gmail.com>
To: Eric Voskuil <eric@voskuil.org>
Content-Type: multipart/alternative; boundary="000000000000aaa5570574952567"
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Wed, 29 Aug 2018 16:10:14 +0000
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Building a Bitcoin API and query system.
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Aug 2018 16:06:56 -0000
--000000000000aaa5570574952567
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Thanks! That is what my main point is.
On Wed, Aug 29, 2018, 8:10 PM Eric Voskuil <eric@voskuil.org> wrote:
> The API implementation is not what is centralizing, nor is full indexatio=
n
> non-scalable. The centralization is in not running the API from a node
> under your own control. This is of course implied by the comment, =E2=80=
=9Cwithout
> the need for syncing=E2=80=9D. In other words it is the deployment cost o=
f the node
> that is centralizing.
>
> Yet if people relied only on bitcoind and never centralized services ther=
e
> would be *no* block explorers (and no secure light wallets), because it
> does not provide remote query and does not fully index.
>
> Block explorers and light wallets are pretty useful, so presumably some
> API must provide these features (ideally with reduced deployment cost).
> That will either be centralized or decentralized services. As such it see=
ms
> wise to encourage the latter, as opposed to questioning whether there is
> any valid block explorer use case.
>
> e
>
>
> > On Aug 28, 2018, at 11:36, Jonas Schnelli via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
> >
> > Hi
> >
> > To give a critical viewpoint on a such API:
> >
> > Such APIs usually result in central validation, meaning that users trus=
t
> API services rather the validating their own data. It break some of the
> fundamental properties of Bitcoin (avoid trusted third parties).
> > Systems or applications depending on a full indexed blockchain (a thus
> such API) do usually scale pretty bad.
> >
> > I=E2=80=99d like to hear some concrete use-cases for a such block explo=
rer(ish)
> API.
> >
> > Thanks
> > =E2=80=94
> > Jonas
> >
> >> Am 26.08.2018 um 21:58 schrieb Blockchain Group via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org>:
> >>
> >> Hello everyone,
> >>
> >> I am C++ & Node.js developer. I want to propose making a new Bitcoin
> API that supports fast quering of Bitcoin blocks and transactions without
> the need for syncing with all previous nodes.
> >>
> >> In a typical case where I want to build a full fleged Bitcoin explorer
> cum wallet system on my end with external APIs, I need to sync my node an=
d
> then query for the information I need to show separately. I am proposing =
a
> unified method of finding/quering the blockchain data with a standardized
> template containing minimal information about the actual mined block or
> transaction yet satify the need of what I want to query.
> >>
> >> I am working on making a template and a support mechanism on Node.js. =
I
> want to propose it as an improvement (BIP). It will be a great help to
> future web developers who want to make something similar.
> >>
> >> Thanks
> >> Sumit Lahiri.
> >> _______________________________________________
> >> bitcoin-dev mailing list
> >> bitcoin-dev@lists.linuxfoundation.org
> >> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> >
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev@lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--000000000000aaa5570574952567
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto">Thanks! That is what my main point is.=C2=A0</div><br><di=
v class=3D"gmail_quote"><div dir=3D"ltr">On Wed, Aug 29, 2018, 8:10 PM Eric=
Voskuil <<a href=3D"mailto:eric@voskuil.org">eric@voskuil.org</a>> w=
rote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">The API implementation is not=
what is centralizing, nor is full indexation non-scalable. The centralizat=
ion is in not running the API from a node under your own control. This is o=
f course implied by the comment, =E2=80=9Cwithout the need for syncing=E2=
=80=9D. In other words it is the deployment cost of the node that is centra=
lizing.<br>
<br>
Yet if people relied only on bitcoind and never centralized services there =
would be *no* block explorers (and no secure light wallets), because it doe=
s not provide remote query and does not fully index.<br>
<br>
Block explorers and light wallets are pretty useful, so presumably some API=
must provide these features (ideally with reduced deployment cost). That w=
ill either be centralized or decentralized services. As such it seems wise =
to encourage the latter, as opposed to questioning whether there is any val=
id block explorer use case.<br>
<br>
e<br>
<br>
<br>
> On Aug 28, 2018, at 11:36, Jonas Schnelli via bitcoin-dev <<a href=
=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank" rel=3D"=
noreferrer">bitcoin-dev@lists.linuxfoundation.org</a>> wrote:<br>
> <br>
> Hi<br>
> <br>
> To give a critical viewpoint on a such API:<br>
> <br>
> Such APIs usually result in central validation, meaning that users tru=
st API services rather the validating their own data. It break some of the =
fundamental properties of Bitcoin (avoid trusted third parties).<br>
> Systems or applications depending on a full indexed blockchain (a thus=
such API) do usually scale pretty bad.<br>
> <br>
> I=E2=80=99d like to hear some concrete use-cases for a such block expl=
orer(ish) API.<br>
> <br>
> Thanks<br>
> =E2=80=94<br>
> Jonas<br>
> <br>
>> Am 26.08.2018 um 21:58 schrieb Blockchain Group via bitcoin-dev &l=
t;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank=
" rel=3D"noreferrer">bitcoin-dev@lists.linuxfoundation.org</a>>:<br>
>> <br>
>> Hello everyone,<br>
>> <br>
>> I am C++ & Node.js developer. I want to propose making a new B=
itcoin API that supports fast quering of Bitcoin blocks and transactions wi=
thout the need for syncing with all previous nodes.<br>
>> <br>
>> In a typical case where I want to build a full fleged Bitcoin expl=
orer cum wallet system on my end with external APIs, I need to sync my node=
and then query for the information I need to show separately. I am proposi=
ng a unified method of finding/quering the blockchain data with a standardi=
zed template containing minimal information about the actual mined block or=
transaction yet satify the need of what I want to query.<br>
>> <br>
>> I am working on making a template and a support mechanism on Node.=
js. I want to propose it as an improvement (BIP). It will be a great help t=
o future web developers who want to make something similar.<br>
>> <br>
>> Thanks<br>
>> Sumit Lahiri.<br>
>> _______________________________________________<br>
>> bitcoin-dev mailing list<br>
>> <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D=
"_blank" rel=3D"noreferrer">bitcoin-dev@lists.linuxfoundation.org</a><br>
>> <a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitc=
oin-dev" rel=3D"noreferrer noreferrer" target=3D"_blank">https://lists.linu=
xfoundation.org/mailman/listinfo/bitcoin-dev</a><br>
> <br>
> _______________________________________________<br>
> bitcoin-dev mailing list<br>
> <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_bl=
ank" rel=3D"noreferrer">bitcoin-dev@lists.linuxfoundation.org</a><br>
> <a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-=
dev" rel=3D"noreferrer noreferrer" target=3D"_blank">https://lists.linuxfou=
ndation.org/mailman/listinfo/bitcoin-dev</a><br>
</blockquote></div>
--000000000000aaa5570574952567--
|
