1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pete@petertodd.org>) id 1WmSTJ-0005Cp-I1
for bitcoin-development@lists.sourceforge.net;
Mon, 19 May 2014 18:39:37 +0000
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;
Received: from outmail148098.authsmtp.com ([62.13.148.98])
by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1WmSTI-0000Av-5T for bitcoin-development@lists.sourceforge.net;
Mon, 19 May 2014 18:39:37 +0000
Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235])
by punt17.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s4JIdThK046298;
Mon, 19 May 2014 19:39:29 +0100 (BST)
Received: from [100.125.13.180] (static.kpn.net [194.151.204.54] (may be
forged)) (authenticated bits=0)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s4JIdN3p094046
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Mon, 19 May 2014 19:39:24 +0100 (BST)
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>
X-Server-Quench: e63236c1-df84-11e3-b396-002590a15da7
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aAdMdwsUFVQNAgsB AmIbWl1eU1R7W2c7 agNVcwRYY1RMXwF0
VUxWRlRXCwQmQhh7 f0pgUVlyfgFGfHg+ YkZiVj4OWkd4dkAu
Q1MAQ2UCeGZhPWMC AkNRcR5UcAFPdx8U a1UrBXRDAzANdhES
HhM4ODE3eDlSNilR RRkIIFQOdA4zFyYx XVgpAC81EEsOVk0A
X-Authentic-SMTP: 61633532353630.1023:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 194.151.204.54/465
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by punt17.authsmtp.com id
s4JIdThK046298
X-Spam-Score: -1.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 SPF_PASS SPF: sender matches SPF record
X-Headers-End: 1WmSTI-0000Av-5T
Subject: Re: [Bitcoin-development] Paper Currency
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: Mon, 19 May 2014 18:39:37 -0000
-----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-----
|
