1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
|
Return-Path: <hearn@vinumeris.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 43980126C
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 18 Sep 2015 16:22:11 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ig0-f182.google.com (mail-ig0-f182.google.com
[209.85.213.182])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id A9A59276
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 18 Sep 2015 16:22:10 +0000 (UTC)
Received: by igbni9 with SMTP id ni9so20893594igb.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 18 Sep 2015 09:22:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=vinumeris.com; s=google;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type;
bh=8rkFXRoqSMH+Swvj+e1Tuj1zm8xzKoGt7xerrVU9DeY=;
b=SoYz/+HxCa0yX5VMPVKpT8wabSy0V821Go1EnjOPM7TWLwxdJ/ECQ4fNnIotBbe+zF
99duMDUyVAmhaRKsGPdJ6sC1UbyjaUqt/FCu0OBLwHLuOMDNACqol0hqbwHGiVkQZEVz
bDOB/mw+K0u2x8+FBlAPucLYoWEce3ecJFE+I=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=8rkFXRoqSMH+Swvj+e1Tuj1zm8xzKoGt7xerrVU9DeY=;
b=MXI9njRfPN23ccK6rY4OTz97gUNEtDebiLTnD+hLBRVi3hnbgUC+2kPRzRQ2VFUYHV
Fr+fDzJ+SD0CczLNRbR/FurVLWbharLB3xUwr+PfcL51ZTQV/wSksQCWd03vObh/13V6
nclKO3T84Z5XXGjrDvAEE9A2nTWdRcVCgD5gxI772o2OtJfVfRfeLsKOMPTrZYRTShCz
Ctp7My7lc5XP0tP3OR6hFFgcq30VH/qpu2rzgRGn3qhKEvJdkzee9tZ9+JXwjer7nanj
bRgKNz0/3pB1dwzOpR1d7O6bAP2djv6/vqHN7FilGmGHQM+D+ARhDnkQHsLwe2iNSLxl
krGw==
X-Gm-Message-State: ALoCoQnJLw+NKTFub4U7OnJaM08Ht29L7oHlug4hfkBGheMOb1WG4DwvcOqdw8Wd1xpibvhogc5z
MIME-Version: 1.0
X-Received: by 10.50.66.146 with SMTP id f18mr34277640igt.83.1442593329973;
Fri, 18 Sep 2015 09:22:09 -0700 (PDT)
Received: by 10.50.192.233 with HTTP; Fri, 18 Sep 2015 09:22:09 -0700 (PDT)
In-Reply-To: <20150918000718.GA5251@amethyst.visucore.com>
References: <CADm_WcY8Vy+k+5BaBS+jV6D6tmSXrok8rAxoPxxKOzUhyPWgMg@mail.gmail.com>
<20150916222928.GC32688@muck>
<20150918000718.GA5251@amethyst.visucore.com>
Date: Fri, 18 Sep 2015 17:22:09 +0100
Message-ID: <CA+w+GKTD02XvaFaZaJmdmOgyER8SeQyqNrpnXyj8fJDMHUDPOA@mail.gmail.com>
From: Mike Hearn <hearn@vinumeris.com>
To: "Wladimir J. van der Laan" <laanwj@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bdc09f6fd2c3e052007ee1c
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham
version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] libconsensus and bitcoin development process
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development 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: Fri, 18 Sep 2015 16:22:11 -0000
--047d7bdc09f6fd2c3e052007ee1c
Content-Type: text/plain; charset=UTF-8
>
> 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.
--047d7bdc09f6fd2c3e052007ee1c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">What one needs for that, I think, is a library t=
hat 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 th=
e way.<br></blockquote><div><br></div><div>This is exactly what SPV librari=
es like bitcoinj do: they know how to build a block locator, request the bl=
ocks forward from the common branch point, and handle re-orgs onto whatever=
the current best chain are by downloading data from a full node.</div><div=
><br></div><div>If your official position is people should all use bitcoinj=
to do things like build extra indexes, then great. Send them our way. It a=
lready knows how to calculate a UTXO set indexed by address.</div></div></d=
iv></div>
--047d7bdc09f6fd2c3e052007ee1c--
|