public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Tom Harding <tomh@thinlink.com>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Address Expiration to Prevent Reuse
Date: Thu, 26 Mar 2015 21:44:11 +0000	[thread overview]
Message-ID: <CAAS2fgSgXdpbT3iqnu_B4j-twAixFBLN9zt=Qid62FrNSkwVdA@mail.gmail.com> (raw)
In-Reply-To: <551479A3.9010104@thinlink.com>

On Thu, Mar 26, 2015 at 9:26 PM, Tom Harding <tomh@thinlink.com> wrote:
> I should have been clearer that the motivation for address expiration is to
> reduce the rate of increase of the massive pile of bitcoin addresses out
> there which have to be monitored forever for future payments.  It could make
> a significant dent if something like this worked, and were used by default
> someday.

Great, that can be accomplished by simply encoding an expiration into
the address people are using and specifying that clients enforce it.



  parent reply	other threads:[~2015-03-26 21:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25  1:57 [Bitcoin-development] Address Expiration to Prevent Reuse Tom Harding
2015-03-25 10:09 ` Matt Whitlock
2015-03-25 16:34 ` Gregory Maxwell
2015-03-25 18:44   ` Tom Harding
2015-03-25 19:22     ` Gregory Maxwell
2015-03-26 20:38       ` Tom Harding
2015-03-26 20:42         ` Gregory Maxwell
2015-03-26 21:26           ` Tom Harding
2015-03-26 21:33             ` Peter Todd
2015-03-26 21:44             ` Gregory Maxwell [this message]
2015-03-26 22:23               ` Tom Harding
2015-03-26 22:28               ` s7r
2015-03-26 23:00                 ` Gregory Maxwell
2015-06-13  4:52               ` odinn
2015-03-27  1:51 Thy Shizzle
2015-03-27  3:13 ` Gregory Maxwell
2015-03-27  4:31 Thy Shizzle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAAS2fgSgXdpbT3iqnu_B4j-twAixFBLN9zt=Qid62FrNSkwVdA@mail.gmail.com' \
    --to=gmaxwell@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=tomh@thinlink.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox