diff options
| author | Mike Hearn <mike@plan99.net> | 2014-03-12 17:41:33 +0100 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2014-03-12 16:41:39 +0000 |
| commit | b2ef2c2e50179a93f69244caa0c309ed75dfb86e (patch) | |
| tree | 613a0b0a481d3a4fbc93c549365c5ad0c2230a01 | |
| parent | 34152e09fac8796025d1b3372201668b51a7a7a3 (diff) | |
| download | pi-bitcoindev-b2ef2c2e50179a93f69244caa0c309ed75dfb86e.tar.gz pi-bitcoindev-b2ef2c2e50179a93f69244caa0c309ed75dfb86e.zip | |
Re: [Bitcoin-development] Multisign payment protocol?
| -rw-r--r-- | 5a/5c45dd8dafc9b5658e76e145ce54f208ea06ab | 114 |
1 files changed, 114 insertions, 0 deletions
diff --git a/5a/5c45dd8dafc9b5658e76e145ce54f208ea06ab b/5a/5c45dd8dafc9b5658e76e145ce54f208ea06ab new file mode 100644 index 000000000..3edc96b70 --- /dev/null +++ b/5a/5c45dd8dafc9b5658e76e145ce54f208ea06ab @@ -0,0 +1,114 @@ +Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] + helo=mx.sourceforge.net) + by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <mh.in.england@gmail.com>) id 1WNmDr-0001ht-Mc + for bitcoin-development@lists.sourceforge.net; + Wed, 12 Mar 2014 16:41:39 +0000 +Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com + designates 209.85.214.173 as permitted sender) + client-ip=209.85.214.173; envelope-from=mh.in.england@gmail.com; + helo=mail-ob0-f173.google.com; +Received: from mail-ob0-f173.google.com ([209.85.214.173]) + by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) + (Exim 4.76) id 1WNmDq-0004ZA-Sc + for bitcoin-development@lists.sourceforge.net; + Wed, 12 Mar 2014 16:41:39 +0000 +Received: by mail-ob0-f173.google.com with SMTP id gq1so10257344obb.32 + for <bitcoin-development@lists.sourceforge.net>; + Wed, 12 Mar 2014 09:41:33 -0700 (PDT) +MIME-Version: 1.0 +X-Received: by 10.60.98.73 with SMTP id eg9mr1016629oeb.81.1394642493536; Wed, + 12 Mar 2014 09:41:33 -0700 (PDT) +Sender: mh.in.england@gmail.com +Received: by 10.76.71.231 with HTTP; Wed, 12 Mar 2014 09:41:33 -0700 (PDT) +In-Reply-To: <CAJHLa0OG4y_+7=z8_nuejHSynw+2CU9fzVGhAet3g0d3BoGCpg@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> +Date: Wed, 12 Mar 2014 17:41:33 +0100 +X-Google-Sender-Auth: YKFkP4KvzJXdS5hhf1vjTu84zdM +Message-ID: <CANEZrP02L2GsPSKFTncwvn95FpEz-LFysro4-Z+f25eRcENL8w@mail.gmail.com> +From: Mike Hearn <mike@plan99.net> +To: Jeff Garzik <jgarzik@bitpay.com> +Content-Type: multipart/alternative; boundary=089e0139fc606b6bac04f46b82f0 +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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider + (mh.in.england[at]gmail.com) + -0.0 SPF_PASS SPF: sender matches SPF record + 1.0 HTML_MESSAGE BODY: HTML included in message + 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: 1WNmDq-0004ZA-Sc +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:41:39 -0000 + +--089e0139fc606b6bac04f46b82f0 +Content-Type: text/plain; charset=UTF-8 + +> +> 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: + +1) Create tx with an estimated fee level +2) Add signatures +3) Submit. If REJECT for too low fees, increment, go to 1 and try again. + +--089e0139fc606b6bac04f46b82f0 +Content-Type: text/html; charset=UTF-8 +Content-Transfer-Encoding: quoted-printable + +<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo= +ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c= +cc solid;padding-left:1ex">Partially signed and multisig transactions withi= +n bitcoind go through<br> + +the raw transaction API, which does absolutely nothing if the sig<br> +pushes the TX to a higher fee level.</blockquote><div><br></div><div>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 see= +m like you need to implement the fee loop in your own app:</div> +<div><br></div><div>1) Create tx with an estimated fee level</div><div>2) A= +dd signatures</div><div>3) Submit. If REJECT for too low fees, increment, g= +o to 1 and try again.</div><div><br></div><div><br></div></div></div></div> + +--089e0139fc606b6bac04f46b82f0-- + + |