From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 5312EC7D for ; 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 ; Wed, 29 Aug 2018 12:26:09 +0000 (UTC) Received: by mail-io0-f176.google.com with SMTP id l14-v6so4302599iob.7 for ; 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: <8AE1517F-88FB-479D-AE89-993A5545D210@jonasschnelli.ch> In-Reply-To: <8AE1517F-88FB-479D-AE89-993A5545D210@jonasschnelli.ch> From: Blockchain Group Date: Wed, 29 Aug 2018 17:55:57 +0530 Message-ID: To: Jonas Schnelli 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 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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
Thanks, I'll check it out.=C2=A0

On Wed, Aug 29, 2018, 12:06 AM Jonas Schn= elli <dev@jonasschnelli.ch&g= t; wrote:
Hi

To give a critical viewpoint on a such API:

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).
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 explorer(= 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 Bitco= in API that supports fast quering of Bitcoin blocks and transactions withou= t 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 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.
>
> 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.
>
> Thanks
> Sumit Lahiri.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfou= ndation.org/mailman/listinfo/bitcoin-dev

--0000000000002dc3ba05749210a9--