Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <pieter.wuille@gmail.com>) id 1XSToq-0003RG-N0
	for bitcoin-development@lists.sourceforge.net;
	Fri, 12 Sep 2014 16:35:32 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.223.178 as permitted sender)
	client-ip=209.85.223.178; envelope-from=pieter.wuille@gmail.com;
	helo=mail-ie0-f178.google.com; 
Received: from mail-ie0-f178.google.com ([209.85.223.178])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1XSTop-0004PA-KF
	for bitcoin-development@lists.sourceforge.net;
	Fri, 12 Sep 2014 16:35:32 +0000
Received: by mail-ie0-f178.google.com with SMTP id tp5so1191644ieb.23
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 12 Sep 2014 09:35:25 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.42.120.16 with SMTP id d16mr10635262icr.35.1410539725579;
	Fri, 12 Sep 2014 09:35:25 -0700 (PDT)
Received: by 10.50.82.72 with HTTP; Fri, 12 Sep 2014 09:35:25 -0700 (PDT)
In-Reply-To: <CAPg+sBiGWAtToC+vmbtiHk13gq3oGEc4-eoAcGtzbSY=Tr+6XA@mail.gmail.com>
References: <CAPg+sBiTURdRAZbyk3guF5YzAAQebo8yY_TuXHUKYDEdLjDUdQ@mail.gmail.com>
	<CAAS2fgSPe=dTayVXz8uFHQN+Sna7+zDcYKJL6UpuJOTq7H6fKg@mail.gmail.com>
	<CAPg+sBh5TXhKM_oxQpHUw-kLiQmyxCTO4nAO2jbnLUEQb=bdBA@mail.gmail.com>
	<CAPg+sBiGWAtToC+vmbtiHk13gq3oGEc4-eoAcGtzbSY=Tr+6XA@mail.gmail.com>
Date: Fri, 12 Sep 2014 18:35:25 +0200
Message-ID: <CAPg+sBgy2uzASCk1fQd2JxBtjSXgRA=qtF8OakZUyrdQJyNoGQ@mail.gmail.com>
From: Pieter Wuille <pieter.wuille@gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
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
	(pieter.wuille[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: 1XSTop-0004PA-KF
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Small update to BIP 62
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: Fri, 12 Sep 2014 16:35:33 -0000

On Mon, Sep 8, 2014 at 1:31 AM, Pieter Wuille <pieter.wuille@gmail.com> wrote:
> I've sent out a new pull request
> (https://github.com/bitcoin/bips/pull/102/files) that:
> * Changes the order of the rules.
> * Adds more reference documentation about minimal pushes and number encodings.
> * Clarified that extra consensus rules cannot prevent someone from
> creating outputs whose spending transactions will be malleable.
>
> I haven't changed which rules are mandatory in v3, so this is a pure
> clarification & reorganization of the text.

Changes: https://github.com/bitcoin/bips/pull/102/files

Gregory, Jeff: does this address your concerns?
Others: comments?

-- 
Pieter