From: Jeff Garzik <jgarzik@bitpay•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Multisign payment protocol?
Date: Wed, 12 Mar 2014 12:57:28 -0400 [thread overview]
Message-ID: <CAJHLa0MqArbLGiELJEnyccc3amsS5p3c2+S1nvUKNSLax0w1yA@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP02L2GsPSKFTncwvn95FpEz-LFysro4-Z+f25eRcENL8w@mail.gmail.com>
On Wed, Mar 12, 2014 at 12:41 PM, Mike Hearn <mike@plan99•net> 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/
next prev parent reply other threads:[~2014-03-12 16:57 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 17:39 Drak
2014-03-10 17:49 ` Gavin Andresen
2014-03-10 18:01 ` Alan Reiner
2014-03-11 0:04 ` kjj
2014-03-11 0:09 ` Alan Reiner
2014-03-11 0:14 ` Jeff Garzik
2014-03-11 1:15 ` Gavin Andresen
2014-03-11 11:43 ` Drak
2014-03-11 12:38 ` Jeff Garzik
2014-03-11 13:51 ` Gavin Andresen
2014-03-11 14:13 ` Jeff Garzik
2014-03-11 14:23 ` Gavin Andresen
2014-03-11 14:34 ` Jeff Garzik
2014-03-11 14:44 ` Jeff Garzik
2014-03-11 14:53 ` Gary Rowe
2014-03-11 15:18 ` Mike Hearn
2014-03-11 17:11 ` Miron
2014-03-11 15:37 ` Thomas Voegtlin
2014-03-11 21:12 ` Peter Todd
2014-03-11 17:41 ` Odinn Cyberguerrilla
2014-03-12 0:29 ` Jean-Pierre Rupp
2014-03-12 2:35 ` Alan Reiner
2014-03-12 2:48 ` Eric Lombrozo
2014-03-12 9:48 ` Mike Hearn
2014-03-12 15:35 ` Jeff Garzik
2014-03-12 16:02 ` Mike Hearn
2014-03-12 16:09 ` Drak
2014-03-12 16:14 ` Mike Hearn
2014-03-12 16:24 ` Peter Todd
2014-03-12 16:33 ` Jeff Garzik
2014-03-12 16:41 ` Mike Hearn
2014-03-12 16:47 ` Peter Todd
2014-03-12 16:57 ` Jeff Garzik [this message]
2014-03-10 17:50 ` Mike Hearn
2014-03-10 18:12 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJHLa0MqArbLGiELJEnyccc3amsS5p3c2+S1nvUKNSLax0w1yA@mail.gmail.com \
--to=jgarzik@bitpay$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox