From: Aymeric Vitte <vitteaymeric@gmail•com>
To: Jonas Schnelli <dev@jonasschnelli•ch>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
Blockchain Group <shekharhiran@gmail•com>
Subject: Re: [bitcoin-dev] Building a Bitcoin API and query system.
Date: Thu, 30 Aug 2018 12:03:41 +0200 [thread overview]
Message-ID: <fc603995-cdb1-2bef-4fdc-e3f0009fb998@gmail.com> (raw)
In-Reply-To: <8AE1517F-88FB-479D-AE89-993A5545D210@jonasschnelli.ch>
Le 28/08/2018 à 20:36, Jonas Schnelli via bitcoin-dev a écrit :
> I’d like to hear some concrete use-cases for a such block explorer(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
next prev parent reply other threads:[~2018-08-30 10:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 19:58 Blockchain Group
2018-08-28 15:15 ` Joseph Gleason ⑈
2018-08-28 15:47 ` Matias Alejo Garcia
2018-08-28 17:34 ` Blockchain Group
2018-08-28 17:51 ` Guido Dassori
2018-08-28 18:14 ` Eric Voskuil
2018-08-28 18:36 ` Jonas Schnelli
2018-08-29 12:25 ` Blockchain Group
2018-08-29 14:40 ` Eric Voskuil
2018-08-29 16:06 ` Blockchain Group
2018-08-29 18:27 ` Jonas Schnelli
2018-08-29 18:29 ` Blockchain Group
2018-08-29 18:45 ` Eric Voskuil
2018-08-30 10:03 ` Aymeric Vitte [this message]
2018-08-30 11:40 ` Blockchain Group
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fc603995-cdb1-2bef-4fdc-e3f0009fb998@gmail.com \
--to=vitteaymeric@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=dev@jonasschnelli$(echo .)ch \
--cc=shekharhiran@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox