From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YaaaF-0003nY-8H for bitcoin-development@lists.sourceforge.net; Wed, 25 Mar 2015 01:58:15 +0000 X-ACL-Warn: Received: from mail-pd0-f175.google.com ([209.85.192.175]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Yaaa8-0002HR-Rl for bitcoin-development@lists.sourceforge.net; Wed, 25 Mar 2015 01:58:15 +0000 Received: by pdnc3 with SMTP id c3so12057812pdn.0 for ; Tue, 24 Mar 2015 18:58:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=5BVtnuDquTlIBX8BZkHUhX0vFA9WSnQ8uQ9x83j2Qdw=; b=aHriziVBNaOVq1KGnaZaxa6B3fXyPFoir8J7xhWVtNJTAvKo0YDrhDOnL8SqqfvqIY ALaZZtPI94Hype4X8aoXT9q0DQsj6wM5s3Jjaz69plp1L5NWi3bIwjMH2mporE+mHCWe KZIyGJCLCpin/fOBH0Nq1D8mpGdH8PR7oloeLzqmIUsgiMKTct6UWyfuxwGEA1cq4aE8 BqzS7Joo9OJWF2fVUvQwmTxAmOkSl764IzSFVvf42fqKG6kgzMjYuO35cT89E0HJqVUh p7XZ5nIYsZCgvAuvKEOSAgtaFO8WewkHy4Mfv3/d1ILfM6fm5hcb33JCHen2vCIJCTsT 3BJA== X-Gm-Message-State: ALoCoQkc1Nt1Ox3MXShLLBkIkCnRv05oP6PAv6115XK+YIhn4HaITUyMTjQa6lGzOAqet2OrZ/IX X-Received: by 10.70.34.129 with SMTP id z1mr12187389pdi.113.1427248682975; Tue, 24 Mar 2015 18:58:02 -0700 (PDT) Received: from [10.100.1.239] ([204.58.254.99]) by mx.google.com with ESMTPSA id n3sm588761pdm.90.2015.03.24.18.58.01 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Mar 2015 18:58:02 -0700 (PDT) Message-ID: <55121611.1030104@thinlink.com> Date: Tue, 24 Mar 2015 18:57:37 -0700 From: Tom Harding User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Bitcoin Development Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.6 RCVD_IN_SORBS_WEB RBL: SORBS: sender is an abusable web server [204.58.254.99 listed in dnsbl.sorbs.net] X-Headers-End: 1Yaaa8-0002HR-Rl Subject: [Bitcoin-development] Address Expiration to Prevent Reuse X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Mar 2015 01:58:15 -0000 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.