1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1X73K6-0002oA-EQ
for bitcoin-development@lists.sourceforge.net;
Tue, 15 Jul 2014 14:03:14 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.212.174 as permitted sender)
client-ip=209.85.212.174; envelope-from=jgarzik@bitpay.com;
helo=mail-wi0-f174.google.com;
Received: from mail-wi0-f174.google.com ([209.85.212.174])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1X73Jy-00047X-Pn
for bitcoin-development@lists.sourceforge.net;
Tue, 15 Jul 2014 14:03:14 +0000
Received: by mail-wi0-f174.google.com with SMTP id d1so4405406wiv.13
for <bitcoin-development@lists.sourceforge.net>;
Tue, 15 Jul 2014 07:03:00 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-type;
bh=BzPdMFYhu1spealoa5xJXyemcKNDvThvKS9+jrm12HA=;
b=EPClOGVTZPu7Zz2DpCd807TE+Enm2ctvMoZns3KrG/a5yy9Wl/KW4bWcqeWGEJUvFl
vjrvdj20QGzDv35W7WVBedpdNZIfysLDJNOsHW5gNXn9GTXccNuUubN5G7ev2taUJ8OD
kD4sP3Jpc2BEilv/2oE3zbNAn4hZP6w+pVaTLwawfAWsFfaX1Spt/iKSohzCpH7BCODP
pc5gHl78HeDjwlvFIJiaFaWHkVOYYXjOt1b4H0C+7L7Zqv9c13F0HkEqXo6JZztUFpx8
i8VKr1TWAkRJZ2wO5ftPmrk7Ucqat05XQohUBTjxAxeapzDRSlbpHtK8ooRomnGLCnht
Ngcg==
X-Gm-Message-State: ALoCoQmrJxT+KPFfDbAJUwyv+2uRtTyV5hE42yAbYXm473rf9HVwE3Mn0nzyr6aZLlbrL8+JZBQV
X-Received: by 10.181.13.44 with SMTP id ev12mr5913586wid.57.1405432980507;
Tue, 15 Jul 2014 07:03:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.5.67 with HTTP; Tue, 15 Jul 2014 07:02:40 -0700 (PDT)
In-Reply-To: <CANEZrP1dWHtEEF7QDdfJe+kb8G+66cHd3-6UpAwkbOF9+sWEcw@mail.gmail.com>
References: <CAJHLa0M7iEUQnJ9M4A3ev3EQqxUVQG85qucRamvMb0n-CztOFA@mail.gmail.com>
<CANEZrP1dWHtEEF7QDdfJe+kb8G+66cHd3-6UpAwkbOF9+sWEcw@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Tue, 15 Jul 2014 10:02:40 -0400
Message-ID: <CAJHLa0P97vqzXdk0-P+XEeo1S0xjc-Dsm8K+GjYxGE_O1TmPcQ@mail.gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.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 SPF_PASS SPF: sender matches SPF record
-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: 1X73Jy-00047X-Pn
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 14:03:14 -0000
BIP70 does not work well for unknown number of future payments of
unknown, unpredictable value.
On Tue, Jul 15, 2014 at 6:25 AM, Mike Hearn <mike@plan99.net> wrote:
>> 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.
>
>
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
