Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.148.98 as permitted sender)
	client-ip=62.13.148.98; envelope-from=pete@petertodd.org;
	helo=outmail148098.authsmtp.com; 
User-Agent: K-9 Mail for Android
In-Reply-To: <537A4B78.7060804@localhost.local>
References: <BAY173-W1475F72C70BC089A82C20FCC300@phx.gbl>
	<CANEZrP27wSZ=aFdW5Nw1gGqemE4GeLbfTS5=DD5uX+fsTfpF3g@mail.gmail.com>
	<537A4B78.7060804@localhost.local>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=UTF-8
From: Peter Todd <pete@petertodd.org>
Date: Mon, 19 May 2014 20:39:21 +0200
To: Justus Ranvier <justusranvier@gmail.com>,
	bitcoin-development@lists.sourceforge.net
Message-ID: <16b400d8-7f1f-408a-9193-2fdde7ed393e@email.android.com>
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Bitcoin-development] Paper Currency
Precedence: list

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256


On 19 May 2014 20:20:40 CEST, Justus Ranvier <justusranvier@gmail.com> wr=
ote:

>You and Gavin could do a lot better by working on a Bitcoin social
>contract - a promise of what features will *never* be added (or taken
>away) from Bitcoin, because despite what you say it's not acceptable
>to propose anything at all.
>
>Maybe start with things like how the Bitcoin protocol will never be
>changed to allow for confiscation of funds, regardless of who might
>demand such a feature.

Might be worth looking into the recent RFC=C2=A07258: Pervasive Monitorin=
g Is an Attack for some guidance on how to write such a social contract.

Re: Gavin, note the language in the foundation bylaws:

Section 2.2 The Corporation shall promote and protect both the decentrali=
zed, distributed and private nature of the Bitcoin distributed-digital cu=
rrency and transaction system as well as individual choice, participation=
 and financial privacy when using such systems.

You might want to do a pull-req to add fungibility and rejection of black=
lists to that list; note Adam Back's comments on how fungibility and priv=
acy are inherently linked.
-----BEGIN PGP SIGNATURE-----
Version: APG v1.1.1

iQFQBAEBCAA6BQJTek/ZMxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8
cGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhYPIB/9/mhDOei8uMGHmzK41
YdL2ezs4LMPLyCRbo9Eu7MDJAMBaMH4VUbomR0tJVPRS191ifa2F/xGYnbDvk/PG
rLX86uPPMBxZqnVMgZLeKJkUHm3Zlkm1Ti58bMR8VVQuPazBBpkYtsvk+0+8j9su
ke7Xq+OqUGOC03bM4bxtKyBCy1FrCJuFgZEywKhOjr6boANLctDRBZerPqQ4AcjP
tHSAAImcesMhjc/N9LJ4MeygszzblYpdsQeiw8jvvyZI7vCSHuKb+hur+kCszYjD
ygfY9QmoNye2yc0GLZd+kXSMwY6gLIvaAFhv2ElMTMiJ7btHtJJfyEaA9Ub4zEEY
JKeO
=3DDSjZ
-----END PGP SIGNATURE-----