From: Mike Hearn <hearn@vinumeris•com>
To: "Wladimir J. van der Laan" <laanwj@gmail•com>
Cc: Bitcoin development mailing list <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] libconsensus and bitcoin development process
Date: Fri, 18 Sep 2015 17:22:09 +0100 [thread overview]
Message-ID: <CA+w+GKTD02XvaFaZaJmdmOgyER8SeQyqNrpnXyj8fJDMHUDPOA@mail.gmail.com> (raw)
In-Reply-To: <20150918000718.GA5251@amethyst.visucore.com>
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
>
> What one needs for that, I think, is a library that communicate with the
> node, and which offers functionality abstractly be similar to 'git pull':
> give me the tree path from my current known tip to the best tip, and supply
> the block hashes (and block data) along the way.
>
This is exactly what SPV libraries like bitcoinj do: they know how to build
a block locator, request the blocks forward from the common branch point,
and handle re-orgs onto whatever the current best chain are by downloading
data from a full node.
If your official position is people should all use bitcoinj to do things
like build extra indexes, then great. Send them our way. It already knows
how to calculate a UTXO set indexed by address.
[-- Attachment #2: Type: text/html, Size: 976 bytes --]
next prev parent reply other threads:[~2015-09-18 16:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 4:10 Jeff Garzik
2015-09-15 9:55 ` Btc Drak
2015-09-15 15:26 ` Jeff Garzik
2015-09-15 16:00 ` Eric Lombrozo
2015-09-15 18:26 ` Btc Drak
2015-09-16 22:29 ` Peter Todd
2015-09-18 0:07 ` Wladimir J. van der Laan
2015-09-18 8:42 ` Eric Lombrozo
2015-09-18 16:22 ` Mike Hearn [this message]
2015-09-22 18:12 ` Jorge Timón
2015-09-22 23:49 ` Dave Scotese
2015-09-23 17:28 ` Jorge Timón
2015-09-29 13:04 ` Jeff Garzik
[not found] ` <CABsx9T0dHxXzemxJN87mU59j4_KZ=zOdwxpXOUe-NhB0ENVMWw@mail.gmail.com>
2015-09-23 16:58 ` Jorge Timón
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+w+GKTD02XvaFaZaJmdmOgyER8SeQyqNrpnXyj8fJDMHUDPOA@mail.gmail.com \
--to=hearn@vinumeris$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=laanwj@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