Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WNm68-0005wN-8H for bitcoin-development@lists.sourceforge.net; Wed, 12 Mar 2014 16:33:40 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com designates 74.125.82.52 as permitted sender) client-ip=74.125.82.52; envelope-from=jgarzik@bitpay.com; helo=mail-wg0-f52.google.com; Received: from mail-wg0-f52.google.com ([74.125.82.52]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WNm67-0001Oq-DU for bitcoin-development@lists.sourceforge.net; Wed, 12 Mar 2014 16:33:40 +0000 Received: by mail-wg0-f52.google.com with SMTP id k14so11586947wgh.11 for ; Wed, 12 Mar 2014 09:33:32 -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=e6zv4fwQX9NbdQx3GRAHbKezZloivQbMm2+CSs780lw=; b=Ucogqe0jRwtSKgiRXskdFp6grqrGib/CEy45hwJwrSip1fNXJkFldPew3LhIS63km9 Pu2u+EB7gRM83aUVEZmou7teggepJg/9oeopLHbevP+zi0SZqlgutclZ26Oc60E6VdDS JBR98IHrniJYZ8kkzXocMaony6vYPGk5AJztjyaoJJ65ngZYSuUxWn4ZcE74fYFWRWDo BjcUR6BCidhyINIu7evHiLTUNjOsB6itWxnVF1hO+/tYQsxFRgBz4K6A3c8u+B+ebchH XJSsgf0F6JFtypssri8pmGOGlaFWdfWHe4fYCcTAds7WbLmadyGdzWgBH1UTvYqPUR7d 7XVg== X-Gm-Message-State: ALoCoQmjbvwkrJ5G8tOGzD5/AWn4/Dh1B8KNp3UNQkxstmulTqlR7doWxo63Eoey0ZH5nLsWBJ+Z X-Received: by 10.194.78.16 with SMTP id x16mr364662wjw.86.1394642012724; Wed, 12 Mar 2014 09:33:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.82.197 with HTTP; Wed, 12 Mar 2014 09:33:12 -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: Jeff Garzik Date: Wed, 12 Mar 2014 12:33:12 -0400 Message-ID: To: Mike Hearn 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 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: 1WNm67-0001Oq-DU 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:33:40 -0000 On Wed, Mar 12, 2014 at 12:02 PM, 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? Partially signed and multisig transactions within bitcoind go through the raw transaction API, which does absolutely nothing if the sig pushes the TX to a higher fee level. -- Jeff Garzik Bitcoin core developer and open source evangelist BitPay, Inc. https://bitpay.com/