1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
|
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 <jgarzik@bitpay.com>) 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 <bitcoin-development@lists.sourceforge.net>;
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: <CANEZrP02L2GsPSKFTncwvn95FpEz-LFysro4-Z+f25eRcENL8w@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>
<CANEZrP2Lr0Do8dPXAvRPkZU0Hk4UBt=CjgXSSKbopawoq8NjgA@mail.gmail.com>
<CAJHLa0OG4y_+7=z8_nuejHSynw+2CU9fzVGhAet3g0d3BoGCpg@mail.gmail.com>
<CANEZrP02L2GsPSKFTncwvn95FpEz-LFysro4-Z+f25eRcENL8w@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Wed, 12 Mar 2014 12:57:28 -0400
Message-ID: <CAJHLa0MqArbLGiELJEnyccc3amsS5p3c2+S1nvUKNSLax0w1yA@mail.gmail.com>
To: Mike Hearn <mike@plan99.net>
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 <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:57:58 -0000
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/
|
