Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <laanwj@gmail.com>) id 1T19AO-0005IL-Py
	for bitcoin-development@lists.sourceforge.net;
	Tue, 14 Aug 2012 04:55:44 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.215.47 as permitted sender)
	client-ip=209.85.215.47; envelope-from=laanwj@gmail.com;
	helo=mail-lpp01m010-f47.google.com; 
Received: from mail-lpp01m010-f47.google.com ([209.85.215.47])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1T19AM-0004u3-CF
	for bitcoin-development@lists.sourceforge.net;
	Tue, 14 Aug 2012 04:55:44 +0000
Received: by lagv3 with SMTP id v3so2302821lag.34
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 13 Aug 2012 21:55:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.152.46.49 with SMTP id s17mr14228031lam.17.1344920135805; Mon,
	13 Aug 2012 21:55:35 -0700 (PDT)
Received: by 10.112.83.161 with HTTP; Mon, 13 Aug 2012 21:55:35 -0700 (PDT)
In-Reply-To: <CA+8xBpevWfyvb7d6dBhMB4s=p4w8GdO7s+WDUo6zoJYGg3+b9A@mail.gmail.com>
References: <CA+8xBpevWfyvb7d6dBhMB4s=p4w8GdO7s+WDUo6zoJYGg3+b9A@mail.gmail.com>
Date: Tue, 14 Aug 2012 06:55:35 +0200
Message-ID: <CA+s+GJD=1TOWB6JH9M2KeKv3vMNezPKGTh7RPYfmRbeFxcxstQ@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Jeff Garzik <jgarzik@exmulti.com>
Content-Type: multipart/alternative; boundary=bcaec5540424f22b9304c7329efb
X-Spam-Score: -0.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
	(laanwj[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-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: 1T19AM-0004u3-CF
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Protocol changes for SPV clients: mempool,
 getdata commands
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: Tue, 14 Aug 2012 04:55:44 -0000

--bcaec5540424f22b9304c7329efb
Content-Type: text/plain; charset=UTF-8

On Mon, Aug 13, 2012 at 5:57 PM, Jeff Garzik <jgarzik@exmulti.com> wrote:

> A small change to the protocol is proposed for satoshi client v0.7
> (upcoming release):
>
>     Add 'mempool' P2P command, and extend 'getdata' behavior
>     https://github.com/bitcoin/bitcoin/pull/1641


Fully agree with the changes, but I think there should be a small BIP, for
consistency, and to make it documented for other client developers.

Wladimir

--bcaec5540424f22b9304c7329efb
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<br><div class=3D"gmail_quote">On Mon, Aug 13, 2012 at 5:57 PM, Jeff Garzik=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:jgarzik@exmulti.com" target=3D"_bl=
ank">jgarzik@exmulti.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">

A small change to the protocol is proposed for satoshi client v0.7<br>
(upcoming release):<br>
<br>
=C2=A0 =C2=A0 Add &#39;mempool&#39; P2P command, and extend &#39;getdata&#3=
9; behavior<br>
=C2=A0 =C2=A0 <a href=3D"https://github.com/bitcoin/bitcoin/pull/1641" targ=
et=3D"_blank">https://github.com/bitcoin/bitcoin/pull/1641</a></blockquote>=
<div><br></div><div>Fully agree with the changes, but I think there should =
be a small BIP, for consistency, and to make it documented for other client=
 developers.</div>

<div><br></div><div>Wladimir</div><div><br></div></div>

--bcaec5540424f22b9304c7329efb--