public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tom Harding <tomh@thinlink.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Address Expiration to Prevent Reuse
Date: Tue, 24 Mar 2015 18:57:37 -0700	[thread overview]
Message-ID: <55121611.1030104@thinlink.com> (raw)

The idea of limited-lifetime addresses was discussed on 2014-07-15 in

http://thread.gmane.org/gmane.comp.bitcoin.devel/5837

It appears that a limited-lifetime address, such as the fanciful

address = 4HB5ld0FzFVj8ALj6mfBsbifRoD4miY36v_349366

where 349366 is the last valid block for a transaction paying this 
address, could be made reuse-proof with bounded resource requirements, 
if for locktime'd tx paying address, the following were enforced by 
consensus:

  - Expiration
    Block containing tx invalid at height > 349366

  - Finality
    Block containing tx invalid if (349366 - locktime) > X
    (X is the address validity duration in blocks)

  - Uniqueness
    Block containing tx invalid if a prior confirmed tx has paid address

Just an an idea, obviously not a concrete proposal.




             reply	other threads:[~2015-03-25  1:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25  1:57 Tom Harding [this message]
2015-03-25 10:09 ` [Bitcoin-development] Address Expiration to Prevent Reuse 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
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=55121611.1030104@thinlink.com \
    --to=tomh@thinlink.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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