From: Tom Harding <tomh@thinlink•com>
To: Gregory Maxwell <gmaxwell@gmail•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Address Expiration to Prevent Reuse
Date: Thu, 26 Mar 2015 14:26:59 -0700 [thread overview]
Message-ID: <551479A3.9010104@thinlink.com> (raw)
In-Reply-To: <CAAS2fgSSOQi4uL95S=GUdXGKZK_y4aNTUoOqkkaLFvzAVPnRig@mail.gmail.com>
On 3/26/2015 1:42 PM, Gregory Maxwell wrote:
> Which is why a simpler, safer, client enforced behavior is probably
> preferable. Someone who wants to go hack their client to make a
> payment that isn't according to the payee will have to live with the
> results, esp. as we can't prevent that in a strong sense.
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.
Address expiration is not an enhancement to the payment experience and
it doesn't stop sender from doing something weird. Hacking a new
address for the recipient would be just as weird as hacking their client
IMHO.
next prev parent reply other threads:[~2015-03-26 21:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 1:57 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 [this message]
2015-03-26 21:33 ` Peter Todd
2015-03-26 21:44 ` Gregory Maxwell
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=551479A3.9010104@thinlink.com \
--to=tomh@thinlink$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gmaxwell@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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