Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <justusranvier@gmail.com>) id 1WmTka-0001Wv-Ts
	for bitcoin-development@lists.sourceforge.net;
	Mon, 19 May 2014 20:01:32 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.223.172 as permitted sender)
	client-ip=209.85.223.172; envelope-from=justusranvier@gmail.com;
	helo=mail-ie0-f172.google.com; 
Received: from mail-ie0-f172.google.com ([209.85.223.172])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WmTkZ-0001j3-6P
	for bitcoin-development@lists.sourceforge.net;
	Mon, 19 May 2014 20:01:32 +0000
Received: by mail-ie0-f172.google.com with SMTP id tp5so3018838ieb.3
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 19 May 2014 13:01:25 -0700 (PDT)
X-Received: by 10.42.58.130 with SMTP id i2mr5658874ich.66.1400529685249;
	Mon, 19 May 2014 13:01:25 -0700 (PDT)
Received: from mail.fuckthenavy.net ([149.255.33.155])
	by mx.google.com with ESMTPSA id mk2sm13284779igb.8.2014.05.19.13.01.23
	for <multiple recipients>
	(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
	Mon, 19 May 2014 13:01:24 -0700 (PDT)
Received: from [10.4.108.214] (unknown [46.19.137.116])
	(using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits))
	(No client certificate requested)
	by mail.fuckthenavy.net (Postfix) with ESMTPSA id D574F207A6;
	Mon, 19 May 2014 20:01:20 +0000 (UTC)
Message-ID: <537A630D.104@localhost.local>
Date: Mon, 19 May 2014 22:01:17 +0200
From: Justus Ranvier <justusranvier@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Gavin Andresen <gavinandresen@gmail.com>
References: <CABsx9T2=nE1c-WOGnQiBqfFQqM0qtPiCcBsWN8pew6JhdpBNOA@mail.gmail.com>
In-Reply-To: <CABsx9T2=nE1c-WOGnQiBqfFQqM0qtPiCcBsWN8pew6JhdpBNOA@mail.gmail.com>
X-Enigmail-Version: 1.6
OpenPGP: id=38450DB5;
	url=http://pool.sks-keyservers.net/pks/lookup?op=get&search=0xC3F7BB2638450DB5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.6 (-)
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
	(justusranvier[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WmTkZ-0001j3-6P
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Working on social contracts (was: 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 20:01:33 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/19/2014 09:41 PM, Gavin Andresen wrote:
> Now I'm really confused.
> 
> Why would Mike or I have the authority to write a "social contract"
> to promise anything about future-Bitcoin?

YOU can make promises about YOUR future behavior. So can everyone else.

The rest of the community can keep track of which developers will and
will not make promises about what changes they will and will not
attempt to implement in Bitcoin, and they can use that information to
make informed decisions about which software they will choose to support.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTemMNAAoJEMP3uyY4RQ21KJMH/1MbnPxZ42sjVjEiGSQBkGfE
E3jt8aAf2DTza8xtybSmT/pHVhx/VUT4UNj9oBZayqJ1eUNr6YMgGCP8J+DxBtN+
mYH4lTnCiR4+hjO9aux0AWFV+hfZSq7A41QH6wymLa5CyywOtc+i7i3qU5ZGrbtX
9yBrQpFilvMIlrAOBDlXUwb06FDK17ZHHX4V5sI8PSRYJvoiWCrk12Vqj1Z95UOy
ayzWGwbO30ky6lGirBXfpu2e2WJADE9sc43ecNCDplUMR4D4n9jwAUldEiMSBKg2
pwUNcfj1gaKkscj4QmGKMbq6yug+lrSa8qq/jFsbQq+2pqT4VjlQlrN52wz7Yeg=
=Jafe
-----END PGP SIGNATURE-----