path: root/ee/205dd767f1ccf2d9cfd8076e02f9b8e92472e3

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 <thyshizzle@outlook.com>) id 1YbJRH-0001VN-KG
	for bitcoin-development@lists.sourceforge.net;
	Fri, 27 Mar 2015 01:51:59 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of outlook.com
	designates 65.54.190.210 as permitted sender)
	client-ip=65.54.190.210; envelope-from=thyshizzle@outlook.com;
	helo=BAY004-OMC4S8.hotmail.com; 
Received: from bay004-omc4s8.hotmail.com ([65.54.190.210])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.76) id 1YbJRF-0001J6-QX
	for bitcoin-development@lists.sourceforge.net;
	Fri, 27 Mar 2015 01:51:59 +0000
Received: from BAY403-EAS383 ([65.54.190.199]) by BAY004-OMC4S8.hotmail.com
	over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751);
	Thu, 26 Mar 2015 18:51:52 -0700
X-TMN: [m21QdvbwpKMpbf9DkSnGzyrV9OHsYbaH]
X-Originating-Email: [thyshizzle@outlook.com]
Message-ID: <BAY403-EAS3839ED2940DD1447E1C0277C2090@phx.gbl>
Content-Type: multipart/alternative;
	boundary="_967b8518-997e-4cec-a737-a9560f8581db_"
MIME-Version: 1.0
To: <s7r@sky-ip.org>, Gregory Maxwell <gmaxwell@gmail.com>, Tom Harding
	<tomh@thinlink.com>
From: Thy Shizzle <thyshizzle@outlook.com>
Date: Fri, 27 Mar 2015 12:51:46 +1100
X-OriginalArrivalTime: 27 Mar 2015 01:51:52.0399 (UTC)
	FILETIME=[98BD0DF0:01D06830]
X-Spam-Score: 0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(thyshizzle[at]outlook.com)
	-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
	no trust [65.54.190.210 listed in list.dnswl.org]
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	1.0 FREEMAIL_REPLY         From and body contain different freemails
X-Headers-End: 1YbJRF-0001J6-QX
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Address Expiration to Prevent Reuse
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 27 Mar 2015 01:51:59 -0000

--_967b8518-997e-4cec-a737-a9560f8581db_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

Yes I agree=2C also there is talks about a government body I know of warmin=
g to bitcoin by issuing addresses for use by a business and then all transa=
ctions can be tracked for that business entity. This is one proposal I saw =
put forward by a country specific bitcoin group to their government and so =
not allowing address reuse would neuter that :(
________________________________
From: s7r<mailto:s7r@sky-ip.org>
Sent: =E2=80=8E27/=E2=80=8E03/=E2=80=8E2015 9:29 AM
To: Gregory Maxwell<mailto:gmaxwell@gmail.com>=3B Tom Harding<mailto:tomh@t=
hinlink.com>
Cc: Bitcoin Development<mailto:bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Address Expiration to Prevent Reuse

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=2C I offer
some services on the internet for free=2C and I only have a bitcoin
address for donations which is posted everywhere. Obviously this could
possibly harm privacy=2C but not everyone who uses bitcoin wants to keep
all transactions private. To the contrary=2C there are accounting cases
when you need to archive all keys=2C 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=2C 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=2C if a certain situation requires it.

On 3/26/2015 11:44 PM=2C Gregory Maxwell wrote:
> On Thu=2C Mar 26=2C 2015 at 9:26 PM=2C Tom Harding <tomh@thinlink.com>
> wrote:
>> 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=2C and were used by default someday.
>
> Great=2C that can be accomplished by simply encoding an expiration
> into the address people are using and specifying that clients
> enforce it.
>
> ----------------------------------------------------------------------
--------
>
>
>
Dive into the World of Parallel Programming The Go Parallel Website=2C
sponsored
> by Intel and developed in partnership with Slashdot Media=2C is your
> hub for all things parallel software development=2C from weekly
> thought leadership blogs to news=2C videos=2C case studies=2C tutorials
> and more. Take a look and join the conversation now.
> http://goparallel.sourceforge.net/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

---------------------------------------------------------------------------=
---
Dive into the World of Parallel Programming The Go Parallel Website=2C spon=
sored
by Intel and developed in partnership with Slashdot Media=2C is your hub fo=
r all
things parallel software development=2C from weekly thought leadership blog=
s to
news=2C videos=2C case studies=2C tutorials and more. Take a look and join =
the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development

--_967b8518-997e-4cec-a737-a9560f8581db_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html=3B charset=3Dutf-8">
</head>
<body>
<div>
<div style=3D"font-family: Calibri=2Csans-serif=3B font-size: 11pt=3B">Yes =
I agree=2C also there is talks about a government body I know of warming to=
 bitcoin by issuing addresses for use by a business and then all transactio=
ns can be tracked for that business entity.
 This is one proposal I saw put forward by a country specific bitcoin group=
 to their government and so not allowing address reuse would neuter that :(=
</div>
</div>
<div dir=3D"ltr">
<hr>
<span style=3D"font-family: Calibri=2Csans-serif=3B font-size: 11pt=3B font=
-weight: bold=3B">From:
</span><span style=3D"font-family: Calibri=2Csans-serif=3B font-size: 11pt=
=3B"><a href=3D"mailto:s7r@sky-ip.org">s7r</a></span><br>
<span style=3D"font-family: Calibri=2Csans-serif=3B font-size: 11pt=3B font=
-weight: bold=3B">Sent:
</span><span style=3D"font-family: Calibri=2Csans-serif=3B font-size: 11pt=
=3B">=E2=80=8E27/=E2=80=8E03/=E2=80=8E2015 9:29 AM</span><br>
<span style=3D"font-family: Calibri=2Csans-serif=3B font-size: 11pt=3B font=
-weight: bold=3B">To:
</span><span style=3D"font-family: Calibri=2Csans-serif=3B font-size: 11pt=
=3B"><a href=3D"mailto:gmaxwell@gmail.com">Gregory Maxwell</a>=3B
<a href=3D"mailto:tomh@thinlink.com">Tom Harding</a></span><br>
<span style=3D"font-family: Calibri=2Csans-serif=3B font-size: 11pt=3B font=
-weight: bold=3B">Cc:
</span><span style=3D"font-family: Calibri=2Csans-serif=3B font-size: 11pt=
=3B"><a href=3D"mailto:bitcoin-development@lists.sourceforge.net">Bitcoin D=
evelopment</a></span><br>
<span style=3D"font-family: Calibri=2Csans-serif=3B font-size: 11pt=3B font=
-weight: bold=3B">Subject:
</span><span style=3D"font-family: Calibri=2Csans-serif=3B font-size: 11pt=
=3B">Re: [Bitcoin-development] Address Expiration to Prevent Reuse</span><b=
r>
<br>
</div>
<div class=3D"BodyFragment">
<div class=3D"PlainText">This should not be enforced by default. There are =
some use cases where<br>
address re-use is justified (a donation address spread on multiple<br>
static pages or even printed on papers/books?). For example=2C I offer<br>
some services on the internet for free=2C and I only have a bitcoin<br>
address for donations which is posted everywhere. Obviously this could<br>
possibly harm privacy=2C but not everyone who uses bitcoin wants to keep<br=
>
all transactions private. To the contrary=2C there are accounting cases<br>
when you need to archive all keys=2C hashes of transactions and<br>
everything (for example when using btc inside a company which is<br>
required by law to keep accounting registries).<br>
<br>
I know it's not recommended to use the same pubkey more than once=2C but<br=
>
the protocol was not designed this way. Enforcing something as<br>
described in this topic will undermine an user's rights to re-use his<br>
addresses=2C if a certain situation requires it.<br>
<br>
On 3/26/2015 11:44 PM=2C Gregory Maxwell wrote:<br>
&gt=3B On Thu=2C Mar 26=2C 2015 at 9:26 PM=2C Tom Harding &lt=3Btomh@thinli=
nk.com&gt=3B <br>
&gt=3B wrote:<br>
&gt=3B&gt=3B I should have been clearer that the motivation for address <br=
>
&gt=3B&gt=3B expiration is to reduce the rate of increase of the massive pi=
le <br>
&gt=3B&gt=3B of bitcoin addresses out there which have to be monitored<br>
&gt=3B&gt=3B forever for future payments.&nbsp=3B It could make a significa=
nt dent<br>
&gt=3B&gt=3B if something like this worked=2C and were used by default some=
day.<br>
&gt=3B <br>
&gt=3B Great=2C that can be accomplished by simply encoding an expiration <=
br>
&gt=3B into the address people are using and specifying that clients <br>
&gt=3B enforce it.<br>
&gt=3B <br>
&gt=3B --------------------------------------------------------------------=
--<br>
--------<br>
&gt=3B<br>
&gt=3B<br>
&gt=3B <br>
Dive into the World of Parallel Programming The Go Parallel Website=2C<br>
sponsored<br>
&gt=3B by Intel and developed in partnership with Slashdot Media=2C is your=
 <br>
&gt=3B hub for all things parallel software development=2C from weekly <br>
&gt=3B thought leadership blogs to news=2C videos=2C case studies=2C tutori=
als <br>
&gt=3B and more. Take a look and join the conversation now. <br>
&gt=3B <a href=3D"http://goparallel.sourceforge.net/">http://goparallel.sou=
rceforge.net/</a>
<br>
&gt=3B _______________________________________________<br>
&gt=3B Bitcoin-development mailing list<br>
&gt=3B Bitcoin-development@lists.sourceforge.net <br>
&gt=3B <a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-deve=
lopment">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</=
a><br>
&gt=3B <br>
<br>
---------------------------------------------------------------------------=
---<br>
Dive into the World of Parallel Programming The Go Parallel Website=2C spon=
sored<br>
by Intel and developed in partnership with Slashdot Media=2C is your hub fo=
r all<br>
things parallel software development=2C from weekly thought leadership blog=
s to<br>
news=2C videos=2C case studies=2C tutorials and more. Take a look and join =
the <br>
conversation now. <a href=3D"http://goparallel.sourceforge.net/">http://gop=
arallel.sourceforge.net/</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
Bitcoin-development@lists.sourceforge.net<br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a><br>
</div>
</div>
</body>
</html>

--_967b8518-997e-4cec-a737-a9560f8581db_--