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 63468BC6 for <bitcoin-dev@lists.linuxfoundation.org>; Thu, 30 Aug 2018 11:41:07 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-it0-f41.google.com (mail-it0-f41.google.com [209.85.214.41]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id F2A2E2C6 for <bitcoin-dev@lists.linuxfoundation.org>; Thu, 30 Aug 2018 11:41:03 +0000 (UTC) Received: by mail-it0-f41.google.com with SMTP id e14-v6so2167831itf.1 for <bitcoin-dev@lists.linuxfoundation.org>; Thu, 30 Aug 2018 04:41:03 -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=rekBnqAETeEY5goU0IpygxkUkN+cPUYRWhJExDMkOiE=; b=PQzsEDSAtcQ6KqDXu5FG+VGTkmwwnNDA/hwKv8X7geebh99ZdZXkF7x4TVNUxz/mwo b3lTi+veNx+EPVlA9+N085jZvwkLWaUkjLsUZE+oNMtIWZGLO3qOI+o8W+8NYFd4QVh6 LLqjAKxVTrZQTT0Zxwsj0eWypV6DSut8oDKBWC16PKIWo8H6jJPlXoY4Pr8y69VixWVZ vEVgX3PBJdxQu1VSaMhz6Rth2VeXxBDIWlUU9ydcledwIQvpEUYkhth+8GVlMUT+Ol3V FT4Ri3aNhgU2AKkURFHc94gP+S/yjgCpFRK8Rm9JQQIbgOhI57lnxKKwiYw9lmXouRVw 6hKw== 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=rekBnqAETeEY5goU0IpygxkUkN+cPUYRWhJExDMkOiE=; b=D/E+noClAYilXtf2/b8LOp7QmP9lT+PHNUxd5MGaNCl8WO0YuTiuH2GsiBL+BEyQI/ 5zkwx3IZCtVqAZ8mtV09bhT3al3oLRDibyP6+TFE8MFwA1bFn8qaeICzGmA+3H+GbJxW wfTtH+MgEXbkX3Bg2rXXMxfHA+mnIUkE9NO0Guj+KDGg9BiDkpHXbUqJGnypC8fdLRdM 3b9n9CByOlyVhuWoUqbzkBPz/cq6EVlAC6ol3U2o4D6GTpUxqC4r7xNbYnXCkDcEeSj1 rS5Kemtpgy+YPl6wP/3iDIHpDa4AdsGgNjX3aGrFb0o1AuPKyQx/qByBXT5ANGAVVAAr KMKA== X-Gm-Message-State: APzg51CgdyI2wo2WEu8GxYK3NcNuiVagWc4Myw8bA7HmxkqjhhZuAFTI ++pGakjdl6w7RQMCdwtRfrUQrj0TNy0QCFnihgQ= X-Google-Smtp-Source: ANB0VdbQFuVGdOTW5MUGIWOH1Rq4BVhLG+6JkXVCz4btmENjIZ9hj2h+GEEQpd3D7qhFjGj2CXg7QAZ/HFTZsF2ZJ/U= X-Received: by 2002:a24:282:: with SMTP id 124-v6mr1608499itu.151.1535629263169; Thu, 30 Aug 2018 04:41:03 -0700 (PDT) MIME-Version: 1.0 References: <CA+9w0-77oP3rmW37R6ty4fF_LhaOtQaL52yQUKynXEmZhQ9MeA@mail.gmail.com> <8AE1517F-88FB-479D-AE89-993A5545D210@jonasschnelli.ch> <fc603995-cdb1-2bef-4fdc-e3f0009fb998@gmail.com> In-Reply-To: <fc603995-cdb1-2bef-4fdc-e3f0009fb998@gmail.com> From: Blockchain Group <shekharhiran@gmail.com> Date: Thu, 30 Aug 2018 17:10:51 +0530 Message-ID: <CA+9w0-4UpbgpXs3xGNuwr9Uem40jRfUKCTR8xPumuHfK_5O0zg@mail.gmail.com> To: Aymeric Vitte <vitteaymeric@gmail.com> Content-Type: multipart/alternative; boundary="000000000000bcf0b30574a58c15" 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: Thu, 30 Aug 2018 11:41:37 +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: Thu, 30 Aug 2018 11:41:07 -0000 --000000000000bcf0b30574a58c15 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks, I'll check it out. On Thu, Aug 30, 2018, 3:33 PM Aymeric Vitte <vitteaymeric@gmail.com> wrote: > > > Le 28/08/2018 =C3=A0 20:36, Jonas Schnelli via bitcoin-dev a =C3=A9crit : > > I=E2=80=99d like to hear some concrete use-cases for a such block explo= rer(ish) > API. > > https://github.com/Ayms/bitcoin-transactions which is somewhere > bitcoin-cli outside of bitcoin core with no wallet, which implies that > you don't want to mix/provide your wallet with/to the app creating your > transactions and/or you don't want to use wallet sw > > Problem: quasi nobody succeeds to use it (and probably this trend is > unlikely to revert), that's why there is https://peersm.com/wallet which > is querying the info outside and output the right command to use with > the tool (or output the transaction if people put their keys, which is > of course not advised unless they are sure that the corresponding > addresses are dead ones) > > It is planned to put the app for the advanced mode (ie people must know > all the parameters) as an offline one inside browsers, then back to the > above problem... > > So probably the offline mode should include a phase where the tool > connects to some APIs/explorers like the one suggested here before > switching to the offline mode to enter the keys, this will always be not > very secure for the query phase unless it can become something > decentralized (and usable the same way on different networks), which as > far as I understand is envisioned here > > -- > Bitcoin transactions made simple: > https://github.com/Ayms/bitcoin-transactions > Zcash wallets made simple: https://github.com/Ayms/zcash-wallets > Bitcoin wallets made simple: https://github.com/Ayms/bitcoin-wallets > Get the torrent dynamic blocklist: http://peersm.com/getblocklist > Check the 10 M passwords list: http://peersm.com/findmyass > Anti-spies and private torrents, dynamic blocklist: > http://torrent-live.org > Peersm : http://www.peersm.com > torrent-live: https://github.com/Ayms/torrent-live > node-Tor : https://www.github.com/Ayms/node-Tor > GitHub : https://www.github.com/Ayms > > > --000000000000bcf0b30574a58c15 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto">Thanks, I'll check it out.=C2=A0</div><br><div class= =3D"gmail_quote"><div dir=3D"ltr">On Thu, Aug 30, 2018, 3:33 PM Aymeric Vit= te <<a href=3D"mailto:vitteaymeric@gmail.com">vitteaymeric@gmail.com</a>= > wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 = 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br> <br> Le 28/08/2018 =C3=A0 20:36, Jonas Schnelli via bitcoin-dev a =C3=A9crit=C2= =A0:<br> > I=E2=80=99d like to hear some concrete use-cases for a such block expl= orer(ish) API.<br> <br> <a href=3D"https://github.com/Ayms/bitcoin-transactions" rel=3D"noreferrer = noreferrer" target=3D"_blank">https://github.com/Ayms/bitcoin-transactions<= /a> which is somewhere<br> bitcoin-cli outside of bitcoin core with no wallet, which implies that<br> you don't want to mix/provide your wallet with/to the app creating your= <br> transactions and/or you don't want to use wallet sw<br> <br> Problem: quasi nobody succeeds to use it (and probably this trend is<br> unlikely to revert), that's why there is <a href=3D"https://peersm.com/= wallet" rel=3D"noreferrer noreferrer" target=3D"_blank">https://peersm.com/= wallet</a> which<br> is querying the info outside and output the right command to use with<br> the tool (or output the transaction if people put their keys, which is<br> of course not advised unless they are sure that the corresponding<br> addresses are dead ones)<br> <br> It is planned to put the app for the advanced mode (ie people must know<br> all the parameters) as an offline one inside browsers, then back to the<br> above problem...<br> <br> So probably the offline mode should include a phase where the tool<br> connects to some APIs/explorers like the one suggested here before<br> switching to the offline mode to enter the keys, this will always be not<br= > very secure for the query phase unless it can become something<br> decentralized (and usable the same way on different networks), which as<br> far as I understand is envisioned here<br> <br> -- <br> Bitcoin transactions made simple: <a href=3D"https://github.com/Ayms/bitcoi= n-transactions" rel=3D"noreferrer noreferrer" target=3D"_blank">https://git= hub.com/Ayms/bitcoin-transactions</a><br> Zcash wallets made simple: <a href=3D"https://github.com/Ayms/zcash-wallets= " rel=3D"noreferrer noreferrer" target=3D"_blank">https://github.com/Ayms/z= cash-wallets</a><br> Bitcoin wallets made simple: <a href=3D"https://github.com/Ayms/bitcoin-wal= lets" rel=3D"noreferrer noreferrer" target=3D"_blank">https://github.com/Ay= ms/bitcoin-wallets</a><br> Get the torrent dynamic blocklist: <a href=3D"http://peersm.com/getblocklis= t" rel=3D"noreferrer noreferrer" target=3D"_blank">http://peersm.com/getblo= cklist</a><br> Check the 10 M passwords list: <a href=3D"http://peersm.com/findmyass" rel= =3D"noreferrer noreferrer" target=3D"_blank">http://peersm.com/findmyass</a= ><br> Anti-spies and private torrents, dynamic blocklist: <a href=3D"http://torre= nt-live.org" rel=3D"noreferrer noreferrer" target=3D"_blank">http://torrent= -live.org</a><br> Peersm : <a href=3D"http://www.peersm.com" rel=3D"noreferrer noreferrer" ta= rget=3D"_blank">http://www.peersm.com</a><br> torrent-live: <a href=3D"https://github.com/Ayms/torrent-live" rel=3D"noref= errer noreferrer" target=3D"_blank">https://github.com/Ayms/torrent-live</a= ><br> node-Tor : <a href=3D"https://www.github.com/Ayms/node-Tor" rel=3D"noreferr= er noreferrer" target=3D"_blank">https://www.github.com/Ayms/node-Tor</a><b= r> GitHub : <a href=3D"https://www.github.com/Ayms" rel=3D"noreferrer noreferr= er" target=3D"_blank">https://www.github.com/Ayms</a><br> <br> <br> </blockquote></div> --000000000000bcf0b30574a58c15--