From: Matias Alejo Garcia <ematiu@gmail.com>
To: fireduck@gmail.com,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Cc: shekharhiran@gmail.com
Subject: Re: [bitcoin-dev] Building a Bitcoin API and query system.
Date: Tue, 28 Aug 2018 12:47:10 -0300 [thread overview]
Message-ID: <CA+vKqYeW9oi5bk8ZtZEvSJnoVzYdZ2+YXoLCSoe=PPCBhzMuvg@mail.gmail.com> (raw)
In-Reply-To: <CA+ASnrGo8HovRSEDSmFaUcC2mV7Cwjy8eXvaBzCFnuiAHVT5zA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2262 bytes --]
Hi Sumit,
Take a look at https://github.com/bitpay/bitcore/tree/v8.0.0, it is a
bitcoin indexing API server, with several modules, like a block explorer, a
wallet module, etc. It is built using Node.js.
matías
On Tue, Aug 28, 2018 at 12:43 PM Joseph Gleason ⑈ via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> For what it is worth, electrum has a lot or possibly all of what you are
> talking about since the electrum servers are designed to quickly answer the
> queries of light clients. So right now, you could sync up an electrum
> server or use an existing public one and send queries to it with json-rpc.
>
>
> https://github.com/kyuupichan/electrumx/blob/master/docs/protocol-methods.rst
>
>
> On Tue, Aug 28, 2018 at 5:36 AM Blockchain Group via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>> 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 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
>> 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
>
--
Matías Alejo Garcia
@ematiu
Roads? Where we're going, we don't need roads!
[-- Attachment #2: Type: text/html, Size: 3694 bytes --]
next prev parent reply other threads:[~2018-08-28 15:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 19:58 [bitcoin-dev] Building a Bitcoin API and query system Blockchain Group
2018-08-28 15:15 ` Joseph Gleason ⑈
2018-08-28 15:47 ` Matias Alejo Garcia [this message]
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
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='CA+vKqYeW9oi5bk8ZtZEvSJnoVzYdZ2+YXoLCSoe=PPCBhzMuvg@mail.gmail.com' \
--to=ematiu@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=fireduck@gmail.com \
--cc=shekharhiran@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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