Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1VscsC-0006Wq-24
	for bitcoin-development@lists.sourceforge.net;
	Mon, 16 Dec 2013 18:26:32 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.219.51 as permitted sender)
	client-ip=209.85.219.51; envelope-from=mh.in.england@gmail.com;
	helo=mail-oa0-f51.google.com; 
Received: from mail-oa0-f51.google.com ([209.85.219.51])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Vscrw-0003uZ-BH
	for bitcoin-development@lists.sourceforge.net;
	Mon, 16 Dec 2013 18:26:31 +0000
Received: by mail-oa0-f51.google.com with SMTP id i7so5469744oag.10
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 16 Dec 2013 10:26:11 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.60.115.164 with SMTP id jp4mr12814216oeb.19.1387218370936;
	Mon, 16 Dec 2013 10:26:10 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.76.92.72 with HTTP; Mon, 16 Dec 2013 10:26:10 -0800 (PST)
In-Reply-To: <CAPg+sBg6Fa2FZ=OkA78c2qte8jpn-S00JCSvbJ82-1XYwTkwXQ@mail.gmail.com>
References: <CANAnSg0QnZQ2BNJRYm1SD4HePZJQZy3GuAejLXYH+rLFn34CtA@mail.gmail.com>
	<1387190808.12225.60115997.547B23B6@webmail.messagingengine.com>
	<CAPg+sBg6Fa2FZ=OkA78c2qte8jpn-S00JCSvbJ82-1XYwTkwXQ@mail.gmail.com>
Date: Mon, 16 Dec 2013 19:26:10 +0100
X-Google-Sender-Auth: ExTwT0GDb2FDeweROuDt2b9EK8Y
Message-ID: <CANEZrP2igjVPOmiOXcfYXbNspeL=9q1QO5=uza6wvMSdnp-y2A@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Pieter Wuille <pieter.wuille@gmail.com>
Content-Type: multipart/alternative; boundary=089e01161b4639c50904edaaf2f1
X-Spam-Score: -0.5 (/)
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
	(mh.in.england[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	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
	0.0 TIME_LIMIT_EXCEEDED    Exceeded time limit / deadline
X-Headers-End: 1Vscrw-0003uZ-BH
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Fees UI warning
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, 16 Dec 2013 18:26:32 -0000

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

On Mon, Dec 16, 2013 at 12:31 PM, Pieter Wuille <pieter.wuille@gmail.com>wrote:

> Will that also mean no longer reusing (change) addresses?
>

Jim seems to be planning some parallel development to what I'm doing, but
HD wallets and stopping address re-use is the current feature I'm working
on for bitcoinj. Only code review and merging takes higher priority at the
moment. So I think we might be able to stop re-using addresses at least on
devices with sufficient memory some time in Q1

--089e01161b4639c50904edaaf2f1
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">On M=
on, Dec 16, 2013 at 12:31 PM, Pieter Wuille <span dir=3D"ltr">&lt;<a href=
=3D"mailto:pieter.wuille@gmail.com" target=3D"_blank">pieter.wuille@gmail.c=
om</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><span style=3D"color:rgb(3=
4,34,34)">Will that also mean no longer reusing (change) addresses?</span><=
/div>
</blockquote><div><br></div><div>Jim seems to be planning some parallel dev=
elopment to what I&#39;m doing, but HD wallets and stopping address re-use =
is the current feature I&#39;m working on for bitcoinj. Only code review an=
d merging takes higher priority at the moment. So I think we might be able =
to stop re-using addresses at least on devices with sufficient memory some =
time in Q1</div>
</div></div></div>

--089e01161b4639c50904edaaf2f1--