summaryrefslogtreecommitdiff
path: root/04/d0e62476568f26444dcb3a1ce6082d0a98216a
blob: 49184c68747708f0546fb246db85facd56eef379 (plain)
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
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 5312EC7D
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 29 Aug 2018 12:26:10 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-io0-f176.google.com (mail-io0-f176.google.com
	[209.85.223.176])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id DD818619
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 29 Aug 2018 12:26:09 +0000 (UTC)
Received: by mail-io0-f176.google.com with SMTP id l14-v6so4302599iob.7
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 29 Aug 2018 05:26:09 -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=Cf6QLFDi1qBcTgLTR+U/KKS/MJb9+Dey3soezgJ4+Eo=;
	b=eadEszy2ZYEcMjzCqL2Orx5YJQFj7vpqW7U4k0rm1pzQZfAYfu0RoxKXBosH36rJDM
	qdmjmlugDaVr9Jb0Dn7lv6kPu6nfju20sff7CmXis57g7kXZwjZMf+4R6D3dRLiIgS0h
	KfLT64Oopu6MK0Tyy3m3d+6BDRQVlAuJxmBOnNAf8WTY/4IhRnEZGRzsFtqWCx2V65Ln
	2vAECHXhYuYM5EXXApVp0ZTdnJCAgijpZHULoVhD/V+63z/lfSrUQMq6IZYNNY0tttKM
	3PNfEIzo8nFr7mjVrVkNdKA6H7NF+YLJUuhmKdTtE3Hw110kSEQi+7GoKJC0v7fI2KY4
	jQbw==
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=Cf6QLFDi1qBcTgLTR+U/KKS/MJb9+Dey3soezgJ4+Eo=;
	b=YKvtxHtJmPECRo7DZNhKnEylCFJP3f+28yLiVeVIwFPYaCW9XE6C6cVTf3fEu3m52j
	zYc8oBmNR8IL99kfNjOsaiwzRMp7Ywm2wEQ8QAikoSj+8vZ4sOQrypVrMisrCyCamrds
	FcjmAGUN1vp0VzgOKR/HSeZKa/dkKO8ghtVLM2Wbt6/pTDIb2czArpyElcLGzdgbBg6v
	52J6HpCMU+tiv5YxGzvaXfQB1reldQSa6P/Crmzzaltx3OP58kF8qS7huJeULgwcXfJZ
	wE4iNRQHDszxBlwYeEfdvLT8ZPRcgMwnNNeCNRLAYswMiCYGlFEghQgBzszT7qlq+jL4
	knrw==
X-Gm-Message-State: APzg51AxlgTo5tqe7cH/fMhAMKSK9Hs5yzbBYBAyiP6EQ110tFm196Lv
	LdV3z7DvSixE9OUWQ46EOWMOmyd2VFgWeSiipVV8Iw==
X-Google-Smtp-Source: ANB0Vdb7bnHxAiaDnBfR/d2W/AXH2Ai3bHlemyRk8q0tcIP1+JaKmrEDabWUbyF2nukZUv5B4LGSRoYhBvl47f7e7Ew=
X-Received: by 2002:a6b:a54b:: with SMTP id
	o72-v6mr5118993ioe.24.1535545569032; 
	Wed, 29 Aug 2018 05:26:09 -0700 (PDT)
MIME-Version: 1.0
References: <CA+9w0-77oP3rmW37R6ty4fF_LhaOtQaL52yQUKynXEmZhQ9MeA@mail.gmail.com>
	<8AE1517F-88FB-479D-AE89-993A5545D210@jonasschnelli.ch>
In-Reply-To: <8AE1517F-88FB-479D-AE89-993A5545D210@jonasschnelli.ch>
From: Blockchain Group <shekharhiran@gmail.com>
Date: Wed, 29 Aug 2018 17:55:57 +0530
Message-ID: <CA+9w0-74PBbFGxCXvQTm=oP+WmRUUaOMWY8QQ-8EyW7TRKvb2Q@mail.gmail.com>
To: Jonas Schnelli <dev@jonasschnelli.ch>
Content-Type: multipart/alternative; boundary="0000000000002dc3ba05749210a9"
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 12:29:55 +0000
Cc: Bitcoin Protocol Discussion <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 12:26:10 -0000

--0000000000002dc3ba05749210a9
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks, I'll check it out.

On Wed, Aug 29, 2018, 12:06 AM Jonas Schnelli <dev@jonasschnelli.ch> wrote:

> Hi
>
> To give a critical viewpoint on a such API:
>
> Such APIs usually result in central validation, meaning that users trust
> 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 explore=
r(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 AP=
I
> 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
>
>

--0000000000002dc3ba05749210a9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Thanks, I&#39;ll check it out.=C2=A0</div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr">On Wed, Aug 29, 2018, 12:06 AM Jonas Schn=
elli &lt;<a href=3D"mailto:dev@jonasschnelli.ch">dev@jonasschnelli.ch</a>&g=
t; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi<br>
<br>
To give a critical viewpoint on a such API:<br>
<br>
Such APIs usually result in central validation, meaning that users trust AP=
I services rather the validating their own data. It break some of the funda=
mental 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 explorer(=
ish) API.<br>
<br>
Thanks<br>
=E2=80=94<br>
Jonas<br>
<br>
&gt; Am 26.08.2018 um 21:58 schrieb Blockchain Group via bitcoin-dev &lt;<a=
 href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank" re=
l=3D"noreferrer">bitcoin-dev@lists.linuxfoundation.org</a>&gt;:<br>
&gt; <br>
&gt; Hello everyone,<br>
&gt; <br>
&gt; I am C++ &amp; Node.js developer. I want to propose making a new Bitco=
in API that supports fast quering of Bitcoin blocks and transactions withou=
t the need for syncing with all previous nodes.<br>
&gt; <br>
&gt; 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 and=
 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 tra=
nsaction yet satify the need of what I want to query.<br>
&gt; <br>
&gt; 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 fu=
ture web developers who want to make something similar.<br>
&gt; <br>
&gt; Thanks<br>
&gt; Sumit Lahiri.<br>
&gt; _______________________________________________<br>
&gt; bitcoin-dev mailing list<br>
&gt; <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_bl=
ank" rel=3D"noreferrer">bitcoin-dev@lists.linuxfoundation.org</a><br>
&gt; <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>
<br>
</blockquote></div>

--0000000000002dc3ba05749210a9--