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; 
MIME-Version: 1.0
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
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?=
Precedence: list

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).