From: Roy Badami <roy@gnomon•org.uk>
To: Gregory Maxwell <gmaxwell@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net,
Andrew Poelstra <asp11@sfu•ca>
Subject: Re: [Bitcoin-development] Key retirement and key compromise
Date: Mon, 25 Mar 2013 21:35:45 +0000 [thread overview]
Message-ID: <20130325213545.GE65880@giles.gnomon.org.uk> (raw)
In-Reply-To: <CAAS2fgQSMvCwmeoFSJUyrcikj0wV_r_hLRDrE_v5sA4xt48PDQ@mail.gmail.com>
On Mon, Mar 25, 2013 at 02:10:53PM -0700, Gregory Maxwell wrote:
> On Mon, Mar 25, 2013 at 1:49 PM, Roy Badami <roy@gnomon•org.uk> wrote:
> > I'm not envisaging something as drastic as changing the rules to make
> > transactions to revoked addresses invalid - just an overlay protocol.
> > Although to be useful such a protocol would have to be pretty much
> > universally implemented by clients.
>
> That is quite drastic enough, as it requires adding more perpetual
> data that must remain in fast lookup for all validating nodes (the set
> of revoked 'addresses').
Maybe it should be possible for addresses to contain expiry dates, so
that revocation lists don't need to hang around forever.
> Keep in mind that this is only improvement for what is a usually
> inadvisable usage of Bitcoin to begin with... you should not be
> reusing addresses.
It may be inadvisable but in many cases it is pretty much unavoidable
as Bitcoin stands today. Granted, the payment protocol will help with
that in many use cases...
roy
prev parent reply other threads:[~2013-03-25 21:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 23:08 Roy Badami
2013-02-25 9:41 ` Jorge Timón
2013-02-25 19:44 ` Peter Vessenes
[not found] ` <20130225172353.GA7782@malakian.dd-wrt>
2013-03-25 20:49 ` Roy Badami
2013-03-25 21:10 ` Gregory Maxwell
2013-03-25 21:35 ` Roy Badami [this message]
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=20130325213545.GE65880@giles.gnomon.org.uk \
--to=roy@gnomon$(echo .)org.uk \
--cc=asp11@sfu$(echo .)ca \
--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