From mboxrd@z Thu Jan  1 00:00:00 1970
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 <mh.in.england@gmail.com>) id 1WNlcQ-0001Xu-BY
	for bitcoin-development@lists.sourceforge.net;
	Wed, 12 Mar 2014 16:02:58 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.219.49 as permitted sender)
	client-ip=209.85.219.49; envelope-from=mh.in.england@gmail.com;
	helo=mail-oa0-f49.google.com; 
Received: from mail-oa0-f49.google.com ([209.85.219.49])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WNlcP-0000EJ-Lf
	for bitcoin-development@lists.sourceforge.net;
	Wed, 12 Mar 2014 16:02:58 +0000
Received: by mail-oa0-f49.google.com with SMTP id g12so10168208oah.22
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 12 Mar 2014 09:02:52 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.133.142 with SMTP id pc14mr35021562oeb.32.1394640172334; 
	Wed, 12 Mar 2014 09:02:52 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.71.231 with HTTP; Wed, 12 Mar 2014 09:02:52 -0700 (PDT)
In-Reply-To: <CAJHLa0OuXyEz6gcq_dQKmGjJQf3cJjFyzjb38RCB3E6-wMLJ0g@mail.gmail.com>
References: <CANAnSg3Bt0e7CfUcJXe96xhU6nqif9ey_vurZMZkSa9OHjHStw@mail.gmail.com>
	<CABsx9T0SMi6Gp4JY=CpHxLEu5pVkvDmnug7PsY7m_dvtT7khzg@mail.gmail.com>
	<531DFDF8.80008@gmail.com> <531E52FE.5090107@jerviss.org>
	<531E5454.1030601@gmail.com>
	<CAJHLa0NZkzQQvMxgCJAJGT=Yn6vrVNK8Bg7RAfAjctpnrfg5zA@mail.gmail.com>
	<CABsx9T3eViYDsEmLm7ceimJNwci3mCOxWoVnVZHrqp7pDmm0+g@mail.gmail.com>
	<CANAnSg2kzPF0886PsQW8chzsWi6Urp+=-x+9bbv8Mv6hmpvBPw@mail.gmail.com>
	<CAJHLa0Mu2kiv3CCme7BPwzWtT++PNLQ2aAKdLyA8LFTtXEg9fg@mail.gmail.com>
	<CABsx9T0Lvg84qFVRbc7Ef4vZEQj9eO7Jhup5PTRLLeuJFvXi-w@mail.gmail.com>
	<4fca6b510dd57d2f92affeb988d2ee5d.squirrel@fulvetta.riseup.net>
	<531FAA55.2020108@xeno-genesis.com> <531FC808.7060709@gmail.com>
	<9A6499BC-E546-45CC-A7EF-5182FC86052D@gmail.com>
	<53202D51.8010008@plan99.net>
	<CAJHLa0OuXyEz6gcq_dQKmGjJQf3cJjFyzjb38RCB3E6-wMLJ0g@mail.gmail.com>
Date: Wed, 12 Mar 2014 17:02:52 +0100
X-Google-Sender-Auth: J6SJ98wmwJ0NnsiFrEnCsJbaZlk
Message-ID: <CANEZrP2Lr0Do8dPXAvRPkZU0Hk4UBt=CjgXSSKbopawoq8NjgA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Jeff Garzik <jgarzik@bitpay.com>
Content-Type: multipart/alternative; boundary=047d7b47289c0fc54004f46af89a
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
	(mh.in.england[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: 1WNlcP-0000EJ-Lf
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Multisign payment protocol?
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, 12 Mar 2014 16:02:58 -0000

--047d7b47289c0fc54004f46af89a
Content-Type: text/plain; charset=UTF-8

>
> This is what bitcoind produces and expects by default, for a partially
> signed transaction.


What happens if the act of filling out the signature pushes the transaction
into a higher fee level?

--047d7b47289c0fc54004f46af89a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">This is what bitcoind produces and expects by de=
fault, for a partially<br>

signed transaction.</blockquote><div><br></div><div>What happens if the act=
 of filling out the signature pushes the transaction into a higher fee leve=
l?=C2=A0</div></div></div></div>

--047d7b47289c0fc54004f46af89a--