Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WNmTe-0004qU-F1 for bitcoin-development@lists.sourceforge.net; Wed, 12 Mar 2014 16:57:58 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com designates 209.85.212.173 as permitted sender) client-ip=209.85.212.173; envelope-from=jgarzik@bitpay.com; helo=mail-wi0-f173.google.com; Received: from mail-wi0-f173.google.com ([209.85.212.173]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WNmTd-0008Om-Fp for bitcoin-development@lists.sourceforge.net; Wed, 12 Mar 2014 16:57:58 +0000 Received: by mail-wi0-f173.google.com with SMTP id f8so2709642wiw.0 for ; Wed, 12 Mar 2014 09:57:50 -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=SAH7HDqjUe5qNTXPHyTO/I61vGrhRAhR8cgoKwaBYyU=; b=h89DzVvkXph52Fy0wU2PqQ4uFWlKUqcuwdxg5eKl1m7fWxiZNrok1Xa65hovGn8YxC QPO7RjL6Eh+GJK4iYEFcko9+/NO2PBI3nt3Uvnwi70VkrqsQbtK9FHX6fYafKUA/BJSf 72ZaUf90eWXBvHB1XAiyMyfOYpaf8wCM7wjM8JiYBbacRaSCyMo+FmgaEFOaQ7ubZdaI EELYQuGf+1b/Kc2jO26U0jvuH2U5FQHM++FfQwemwCejdGr1qIgnuSwEshJNrFshnYkw ECxGfmEmWkrInOwrSaHx957JvpgttBNinFyATytCbm6804g7Swe7kJK5LZ6IY0PooOba slFA== X-Gm-Message-State: ALoCoQmGwpZQrqODGYxsaYa+Y3ZUFBLjvv5OCejL4KdwI7MWRKnqXK+X5Zdc/Os2xiQ3IBp6bhPc X-Received: by 10.194.174.42 with SMTP id bp10mr2301184wjc.57.1394643470013; Wed, 12 Mar 2014 09:57:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.82.197 with HTTP; Wed, 12 Mar 2014 09:57:28 -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:57:28 -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: 1WNmTd-0008Om-Fp 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:57:58 -0000 On Wed, Mar 12, 2014 at 12:41 PM, Mike Hearn wrote: >> 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. > > > Well, we'll have to make sure this is carefully and loudly documented in the > new developer part of the website that's being worked on. Because this seems > like a recipe for people writing flaky apps. In practice it would seem like > you need to implement the fee loop in your own app: It's the raw transaction API. If you break something, you get to keep both pieces. On a related note, sipa has proposed a more useful raw transaction API call, that figures out fees, change and other details: https://github.com/bitcoin/bitcoin/issues/3794 -- Jeff Garzik Bitcoin core developer and open source evangelist BitPay, Inc. https://bitpay.com/