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 <pieter.wuille@gmail.com>) id 1YxQS4-0007SC-Ee
	for bitcoin-development@lists.sourceforge.net;
	Wed, 27 May 2015 01:48:12 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.214.173 as permitted sender)
	client-ip=209.85.214.173; envelope-from=pieter.wuille@gmail.com;
	helo=mail-ob0-f173.google.com; 
Received: from mail-ob0-f173.google.com ([209.85.214.173])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1YxQS3-0005q8-F9
	for bitcoin-development@lists.sourceforge.net;
	Wed, 27 May 2015 01:48:12 +0000
Received: by obew15 with SMTP id w15so27148786obe.1
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 26 May 2015 18:48:06 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.87.36 with SMTP id u4mr16341596obz.50.1432691286028;
	Tue, 26 May 2015 18:48:06 -0700 (PDT)
Received: by 10.60.94.36 with HTTP; Tue, 26 May 2015 18:48:05 -0700 (PDT)
Received: by 10.60.94.36 with HTTP; Tue, 26 May 2015 18:48:05 -0700 (PDT)
Date: Tue, 26 May 2015 18:48:05 -0700
Message-ID: <CAPg+sBg5TqQ=zjyZ7dp-d1oBGp31Krnix3zyt9suP4-AGbxW=Q@mail.gmail.com>
From: Pieter Wuille <pieter.wuille@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=089e013d0ddc2d39770517066fd3
X-Spam-Score: -0.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
	(pieter.wuille[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-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: 1YxQS3-0005q8-F9
Subject: [Bitcoin-development] Version bits proposal
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: Wed, 27 May 2015 01:48:12 -0000

--089e013d0ddc2d39770517066fd3
Content-Type: text/plain; charset=UTF-8

Hello everyone,

here is a proposal for how to coordinate future soft-forking consensus
changes: https://gist.github.com/sipa/bf69659f43e763540550

It supports multiple parallel changes, as well as changes that get
permanently rejected without obstructing the rollout of others.

Feel free to comment. As the gist does not support notifying participants
of new comments, I would suggest using the mailing list instead.

This is joint work with Peter Todd and Greg Maxwell.

-- 
Pieter

--089e013d0ddc2d39770517066fd3
Content-Type: text/html; charset=UTF-8

<p dir="ltr">Hello everyone,</p>
<p dir="ltr">here is a proposal for how to coordinate future soft-forking consensus changes: <a href="https://gist.github.com/sipa/bf69659f43e763540550">https://gist.github.com/sipa/bf69659f43e763540550</a></p>
<p dir="ltr">It supports multiple parallel changes, as well as changes that get permanently rejected without obstructing the rollout of others.</p>
<p dir="ltr">Feel free to comment. As the gist does not support notifying participants of new comments, I would suggest using the mailing list instead.</p>
<p dir="ltr">This is joint work with Peter Todd and Greg Maxwell.</p>
<p dir="ltr">-- <br>
Pieter<br>
</p>

--089e013d0ddc2d39770517066fd3--