From: Gregory Maxwell <gmaxwell@gmail•com>
To: Thy Shizzle <thyshizzle@outlook•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Address Expiration to Prevent Reuse
Date: Fri, 27 Mar 2015 03:13:06 +0000 [thread overview]
Message-ID: <CAAS2fgSAY=2mMZzw0L5Z=nxnVP5+EE2GL0s6ZgyY5NRRfaTq8A@mail.gmail.com> (raw)
In-Reply-To: <BAY403-EAS3839ED2940DD1447E1C0277C2090@phx.gbl>
On Fri, Mar 27, 2015 at 1:51 AM, Thy Shizzle <thyshizzle@outlook•com> wrote:
> Yes I agree, 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
> transactions 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 :(
I hope you're mistaken, because that would be a serious attack on the
design of bitcoin, which obtains privacy and fungibility, both
essential properties of any money like good, almost exclusively
through avoiding reuse.
[What business would use a money where all their competition can see
their sales and identify their customers, where their customers can
track their margins and suppliers? What individuals would use a system
where their inlaws could criticize their spending? Where their
landlord knows they got a raise, or where thieves know their net
worth?]
Though no one here is currently suggesting blocking reuse as a network
rule, the reasonable and expected response to what you're suggesting
would be to do so.
If some community wishes to choose not to use Bitcoin, great, but they
don't get to simply choose to screw up its utility for all the other
users.
You should advise this "country specific bitcoin group" that they
shouldn't speak for the users of a system which they clearly do not
understand.
next prev parent reply other threads:[~2015-03-27 3:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 1:51 Thy Shizzle
2015-03-27 3:13 ` Gregory Maxwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-27 4:31 Thy Shizzle
2015-03-25 1:57 Tom Harding
2015-03-25 10:09 ` 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
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='CAAS2fgSAY=2mMZzw0L5Z=nxnVP5+EE2GL0s6ZgyY5NRRfaTq8A@mail.gmail.com' \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=thyshizzle@outlook$(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