From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YbGH5-0001pG-GM for bitcoin-development@lists.sourceforge.net; Thu, 26 Mar 2015 22:29:15 +0000 Received-SPF: neutral (sog-mx-1.v43.ch3.sourceforge.com: 162.222.225.29 is neither permitted nor denied by domain of sky-ip.org) client-ip=162.222.225.29; envelope-from=s7r@sky-ip.org; helo=outbound.mailhostbox.com; Received: from outbound.mailhostbox.com ([162.222.225.29]) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1YbGGs-0004Aj-HS for bitcoin-development@lists.sourceforge.net; Thu, 26 Mar 2015 22:29:15 +0000 Received: from [0.0.0.0] (manning2.torservers.net [96.44.189.101]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: s7r@sky-ip.org) by outbound.mailhostbox.com (Postfix) with ESMTPSA id 8029B869645; Thu, 26 Mar 2015 22:28:48 +0000 (GMT) Message-ID: <5514881A.5010006@sky-ip.org> Date: Fri, 27 Mar 2015 00:28:42 +0200 From: s7r User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Gregory Maxwell , Tom Harding References: <55121611.1030104@thinlink.com> <551301F0.9020806@thinlink.com> <55146E2C.9020105@thinlink.com> <551479A3.9010104@thinlink.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252 X-CTCH-RefID: str=0001.0A020205.55148826.0049, ss=1, re=0.001, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown X-CTCH-Score: 0.001 X-CTCH-Rules: C_4847, X-CTCH-Flags: 0 X-CTCH-ScoreCust: 0.000 X-CTCH-SenderID: s7r@sky-ip.org X-CTCH-SenderID-TotalMessages: 1 X-CTCH-SenderID-TotalSpam: 0 X-CTCH-SenderID-TotalSuspected: 0 X-CTCH-SenderID-TotalBulk: 0 X-CTCH-SenderID-TotalConfirmed: 0 X-CTCH-SenderID-TotalRecipients: 0 X-CTCH-SenderID-TotalVirus: 0 X-CTCH-SenderID-BlueWhiteFlag: 0 X-Scanned-By: MIMEDefang 2.72 on 172.18.214.93 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.8 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [162.222.225.29 listed in list.dnswl.org] -0.0 SPF_HELO_PASS SPF: HELO matches SPF record 0.7 SPF_NEUTRAL SPF: sender does not match SPF record (neutral) 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Headers-End: 1YbGGs-0004Aj-HS Cc: Bitcoin Development Subject: Re: [Bitcoin-development] Address Expiration to Prevent Reuse X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list Reply-To: s7r@sky-ip.org List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Mar 2015 22:29:15 -0000 This should not be enforced by default. There are some use cases where address re-use is justified (a donation address spread on multiple static pages or even printed on papers/books?). For example, I offer some services on the internet for free, and I only have a bitcoin address for donations which is posted everywhere. Obviously this could possibly harm privacy, but not everyone who uses bitcoin wants to keep all transactions private. To the contrary, there are accounting cases when you need to archive all keys, hashes of transactions and everything (for example when using btc inside a company which is required by law to keep accounting registries). I know it's not recommended to use the same pubkey more than once, but the protocol was not designed this way. Enforcing something as described in this topic will undermine an user's rights to re-use his addresses, if a certain situation requires it. On 3/26/2015 11:44 PM, Gregory Maxwell wrote: > On Thu, Mar 26, 2015 at 9:26 PM, Tom Harding =20 > wrote: >> I should have been clearer that the motivation for address=20 >> expiration is to reduce the rate of increase of the massive pile=20 >> 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. >=20 > Great, that can be accomplished by simply encoding an expiration=20 > into the address people are using and specifying that clients=20 > enforce it. >=20 > ---------------------------------------------------------------------- -------- > > >=20 Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your=20 > hub for all things parallel software development, from weekly=20 > thought leadership blogs to news, videos, case studies, tutorials=20 > and more. Take a look and join the conversation now.=20 > http://goparallel.sourceforge.net/=20 > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net=20 > https://lists.sourceforge.net/lists/listinfo/bitcoin-development >=20