Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WxcnW-0004Vc-G2 for bitcoin-development@lists.sourceforge.net; Thu, 19 Jun 2014 13:54:38 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.44 as permitted sender) client-ip=209.85.213.44; envelope-from=gavinandresen@gmail.com; helo=mail-yh0-f44.google.com; Received: from mail-yh0-f44.google.com ([209.85.213.44]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WxcnU-0001w5-O1 for bitcoin-development@lists.sourceforge.net; Thu, 19 Jun 2014 13:54:38 +0000 Received: by mail-yh0-f44.google.com with SMTP id f10so1747237yha.3 for ; Thu, 19 Jun 2014 06:54:31 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.236.141.148 with SMTP id g20mr4287507yhj.151.1403186071179; Thu, 19 Jun 2014 06:54:31 -0700 (PDT) Sender: gavinandresen@gmail.com Received: by 10.170.233.194 with HTTP; Thu, 19 Jun 2014 06:54:31 -0700 (PDT) In-Reply-To: <20140619100909.GA3544@savin> References: <20140618001503.GA8360@savin> <20140619100909.GA3544@savin> Date: Thu, 19 Jun 2014 09:54:31 -0400 X-Google-Sender-Auth: sPKravHmHTmvEqMHZ3Gf8jv12y0 Message-ID: From: Gavin Andresen To: Peter Todd Content-Type: multipart/alternative; boundary=20cf303b3e2553a24a04fc30b71e X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gavinandresen[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 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: 1WxcnU-0001w5-O1 Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Proposal: relax the IsStandard rules for P2SH transactions X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jun 2014 13:54:38 -0000 --20cf303b3e2553a24a04fc30b71e Content-Type: text/plain; charset=UTF-8 RE: soft-forks bumping version numbers: Yes, we have consensus that is the way we will do it. I should probably turn https://gist.github.com/gavinandresen/2355445 into an informational BIP. RE: malleability: Orthogonal (but related) issue to IsStandard. Detecting Scripts that leave extra items on the stack will be done in a different part of the code than the code addressed by this pull reques. No need to execute the Script twice to figure out if it leaves extra stuff, and the idea behind IsStandard is to get to a quick yes/no before running a potentially expensive Script execution. -- -- Gavin Andresen Chief Scientist, Bitcoin Foundation https://www.bitcoinfoundation.org/ --20cf303b3e2553a24a04fc30b71e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
RE: soft-forks bumping version numbers:

Yes, we have consensus that is the way we will do it. =C2=A0I should proba= bly turn=C2=A0htt= ps://gist.github.com/gavinandresen/2355445 into an informational BIP.

RE: malleability:

Orthogonal (= but related) issue to IsStandard.

Detecting Script= s that leave extra items on the stack will be done in a different part of t= he code than the code addressed by this pull reques. No need to execute the= Script twice to figure out if it leaves extra stuff, and the idea behind I= sStandard is to get to a quick yes/no before running a potentially expensiv= e Script execution.


<= div class=3D"gmail_extra">

--
--
Gavin Andresen
=
Chief Scientist, Bitcoin Foundation

--20cf303b3e2553a24a04fc30b71e--