Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <jgarzik@exmulti.com>) id 1T0x1q-0000Iz-Sp
	for bitcoin-development@lists.sourceforge.net;
	Mon, 13 Aug 2012 15:58:06 +0000
X-ACL-Warn: 
Received: from mail-qa0-f47.google.com ([209.85.216.47])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1T0x1o-0000Vq-Kb
	for bitcoin-development@lists.sourceforge.net;
	Mon, 13 Aug 2012 15:58:06 +0000
Received: by qadc11 with SMTP id c11so1152545qad.13
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 13 Aug 2012 08:57:59 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:date:message-id:subject:from:to
	:content-type:x-gm-message-state;
	bh=pmZNmKj+Nada3mJa8Hmkbwpky5UlQxSQ97xar5Q7HD8=;
	b=TLiMFnUky962A0Ow3VyqiDRE8mUB+Sl/j+MTk50/fpSEI1KDDd+x8EiPaLsP+zAWwm
	Wp+JB7d3VFAStQ+vnX83R6ep9eVuRevkgMjImt2KEYSJZONATiNGyprrje5Rh1advjAM
	pOJyrk3Gi8p9P9C1a7Si9CekqcHaZQlysOPS49hDsi7vNONi6btP6J5oAuw4rLYzFwqX
	380hoS/ONWOSZKb3hW7L/qCkO+Sr1XWNG/l4D8wNNKw7ILh+RxCrj0hroNLNm01TDJ2A
	+2i/1dWYPVQkUkMmFNj5ipyUQkEiafX3SuyUA6qX86BRPHsbi6fsPbPDwc1NMK0oxdjd
	Tcfw==
MIME-Version: 1.0
Received: by 10.224.106.138 with SMTP id x10mr26487725qao.1.1344873479024;
	Mon, 13 Aug 2012 08:57:59 -0700 (PDT)
Received: by 10.49.35.195 with HTTP; Mon, 13 Aug 2012 08:57:59 -0700 (PDT)
X-Originating-IP: [2001:4830:1603:2:21c:c0ff:fe79:c8c2]
Date: Mon, 13 Aug 2012 11:57:59 -0400
Message-ID: <CA+8xBpevWfyvb7d6dBhMB4s=p4w8GdO7s+WDUo6zoJYGg3+b9A@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQmizl63LtyyP1ZjM6jopgZOb3byrP+f7VYd1wQIWRrECqfYiqpc9v4tGSgVtEBgEJ/OQSV4
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1T0x1o-0000Vq-Kb
Subject: [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: Mon, 13 Aug 2012 15:58:07 -0000

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

The genesis of this command is to permit SPV clients to access the
memory pool, but secondary uses include diagnostics and miner download
(so that miners won't miss lucrative TX's due to node restart).
"getdata" behavior is extended to include any memory pool transaction,
relaxing a previous "getdata" restriction.

Didn't feel this warranted a BIP, but can write one if people really want one.

-- 
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com