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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gmaxwell@gmail.com>) id 1WdYEl-00064o-RR
for bitcoin-development@lists.sourceforge.net;
Fri, 25 Apr 2014 04:59:47 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.217.177 as permitted sender)
client-ip=209.85.217.177; envelope-from=gmaxwell@gmail.com;
helo=mail-lb0-f177.google.com;
Received: from mail-lb0-f177.google.com ([209.85.217.177])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WdYEj-0000mh-VE
for bitcoin-development@lists.sourceforge.net;
Fri, 25 Apr 2014 04:59:47 +0000
Received: by mail-lb0-f177.google.com with SMTP id z11so2661442lbi.36
for <bitcoin-development@lists.sourceforge.net>;
Thu, 24 Apr 2014 21:59:39 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.18.135 with SMTP id w7mr4040594lad.29.1398401979148;
Thu, 24 Apr 2014 21:59:39 -0700 (PDT)
Received: by 10.112.89.68 with HTTP; Thu, 24 Apr 2014 21:59:39 -0700 (PDT)
In-Reply-To: <5359EA1C.6050404@certimix.com>
References: <5359EA1C.6050404@certimix.com>
Date: Thu, 24 Apr 2014 21:59:39 -0700
Message-ID: <CAAS2fgQCX5jgHa43s2uAKWK2uPH_nH=AZu+ksJYm48mpQT9vCg@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Sergio Lerner <sergiolerner@certimix.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gmaxwell[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WdYEj-0000mh-VE
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development]
=?utf-8?q?SmartSPV_=E2=80=93_A_better_Simpl?=
=?utf-8?q?ified_Payment_Verification_for_Smartphones?=
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 04:59:48 -0000
On Thu, Apr 24, 2014 at 9:52 PM, Sergio Lerner
<sergiolerner@certimix.com> wrote:
> In a previous e-mail Mike Hearn asked me how I was going to handle 17K block
> headers a day in my NimbleCoin currency in a the SPV mode.
> I designed a variation of the standard headers-only SPV mode I called
> SmartSPV. This mode could also be implemented by BitcoinJ for Bitcoin.
If you are freely specifying things, and you control the headers than
you can can already make SPV evaluations of work have log(n) scaling.
See: https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg04318.html
(wrt headers in reverse, perhaps you might also want to mine
https://en.bitcoin.it/wiki/User:Gmaxwell/Reverse_header-fetching_sync
for ideas).
|
