Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	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 1X6zv2-0006VQ-Lv
	for bitcoin-development@lists.sourceforge.net;
	Tue, 15 Jul 2014 10:25:08 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.219.50 as permitted sender)
	client-ip=209.85.219.50; envelope-from=mh.in.england@gmail.com;
	helo=mail-oa0-f50.google.com; 
Received: from mail-oa0-f50.google.com ([209.85.219.50])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1X6zv1-0003ib-QP
	for bitcoin-development@lists.sourceforge.net;
	Tue, 15 Jul 2014 10:25:08 +0000
Received: by mail-oa0-f50.google.com with SMTP id g18so5617475oah.37
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 15 Jul 2014 03:25:02 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.181.74 with SMTP id du10mr24768824obc.52.1405419902361; 
	Tue, 15 Jul 2014 03:25:02 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.35.234 with HTTP; Tue, 15 Jul 2014 03:25:02 -0700 (PDT)
In-Reply-To: <CAJHLa0M7iEUQnJ9M4A3ev3EQqxUVQG85qucRamvMb0n-CztOFA@mail.gmail.com>
References: <CAJHLa0M7iEUQnJ9M4A3ev3EQqxUVQG85qucRamvMb0n-CztOFA@mail.gmail.com>
Date: Tue, 15 Jul 2014 12:25:02 +0200
X-Google-Sender-Auth: 9RmCjT1bjbvGX5UyYDpHVJhuK7s
Message-ID: <CANEZrP1dWHtEEF7QDdfJe+kb8G+66cHd3-6UpAwkbOF9+sWEcw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Jeff Garzik <jgarzik@bitpay.com>
Content-Type: multipart/alternative; boundary=089e0118479a0a679504fe38d241
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
X-Headers-End: 1X6zv1-0003ib-QP
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin address TTL & key expiration?
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, 15 Jul 2014 10:25:08 -0000

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

>
> The request:   It would be useful to limit the lifetime of a bitcoin
> address.


Not only useful but essential! Otherwise mobile clients can run out of RAM
and have to cycle around and reuse addresses.

Which is indeed why BIP70 has this feature. It was thought about quite some
time ago. Addresses are an evolutionary dead end, they will never do
everything we need them to do. If there's somewhere that's using addresses,
that's somewhere we will eventually need to upgrade to use BIP70 instead.

--089e0118479a0a679504fe38d241
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"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">The request: =C2=A0 It would be useful to limit =
the lifetime of a bitcoin<br>

address.</blockquote><div><br></div><div>Not only useful but essential! Oth=
erwise mobile clients can run out of RAM and have to cycle around and reuse=
 addresses.=C2=A0</div><div><br></div><div>Which is indeed why BIP70 has th=
is feature. It was thought about quite some time ago. Addresses are an evol=
utionary dead end, they will never do everything we need them to do. If the=
re&#39;s somewhere that&#39;s using addresses, that&#39;s somewhere we will=
 eventually need to upgrade to use BIP70 instead.</div>
<div><br></div><div><br></div></div></div></div>

--089e0118479a0a679504fe38d241--