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 ) id 1WNlis-0002Hv-Nj for bitcoin-development@lists.sourceforge.net; Wed, 12 Mar 2014 16:09:38 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of zikula.org designates 74.125.82.46 as permitted sender) client-ip=74.125.82.46; envelope-from=drak@zikula.org; helo=mail-wg0-f46.google.com; Received: from mail-wg0-f46.google.com ([74.125.82.46]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WNlir-0000TP-Ov for bitcoin-development@lists.sourceforge.net; Wed, 12 Mar 2014 16:09:38 +0000 Received: by mail-wg0-f46.google.com with SMTP id b13so5493111wgh.29 for ; Wed, 12 Mar 2014 09:09:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=PRZbC6b1rP2ggRcaYPie3ToyZ0q3iLzGzuAZ0LjOv5o=; b=O3acaVwb9w9ABBVBdyf9FNMtMcdQDxwQR1CVjRnOBUre8RmhTyaV8nnJH5eI1NS6TK K/iLkzMRNMSO6oBsetny4ULyWFGiHxa9ANOmpjXJm8C5INTq3RjVbBRnHSYIwgVwIFyQ zQ8Gd/XRG8ud0TKXUP+iGLX1LuYBi+Vr9IIGlJCK4nxU/KNdBpC67jiP0o4S/rhdXLOS feZYzEKfdmqmNloOItLU7fWwW9bD7364YVzNPzM4Yd/Etn6uEZocSMbGGUn+RaWtgN4d t5m/zuoGnrcpZxy0oja5wfsiViDfYUrxLdP8zE2DLjzkSYn6Ltwq582Y/vojCg75dWwK 7ZJQ== X-Gm-Message-State: ALoCoQlqYSEaJWc64c9qQn0iaOd1mEYSxAr1XH9BugzaTcaSJTa4feM4efUW5UiFreeFo1i/CIks X-Received: by 10.180.77.129 with SMTP id s1mr8066187wiw.56.1394640571320; Wed, 12 Mar 2014 09:09:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.205.69 with HTTP; Wed, 12 Mar 2014 09:09:11 -0700 (PDT) In-Reply-To: References: <531DFDF8.80008@gmail.com> <531E52FE.5090107@jerviss.org> <531E5454.1030601@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> From: Drak Date: Wed, 12 Mar 2014 16:09:11 +0000 Message-ID: To: Mike Hearn Content-Type: multipart/alternative; boundary=f46d043c801ed7e88904f46b0f5c 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 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1WNlir-0000TP-Ov Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Multisign payment protocol? 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: Wed, 12 Mar 2014 16:09:38 -0000 --f46d043c801ed7e88904f46b0f5c Content-Type: text/plain; charset=UTF-8 On 12 March 2014 16:02, Mike Hearn wrote: > 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? > Can this be calculated in advance knowing the initial transaction size and the number of signatures required? Should be quite easy to make an estimation from that? It's probably more of an implementation detail though... Drak --f46d043c801ed7e88904f46b0f5c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On 1= 2 March 2014 16:02, Mike Hearn <mike@plan99.net> wrote:
This is what bitcoind produces a= nd expects by default, for a partially
signed transaction.

What happens if t= he act of filling out the signature pushes the transaction into a higher fe= e level?=C2=A0

Can = this be calculated in advance knowing the initial transaction size and the = number of signatures required? Should be quite easy to make an estimation f= rom that? It's probably more of an implementation detail though...

Drak
--f46d043c801ed7e88904f46b0f5c--