diff options
| author | Jeff Garzik <jgarzik@bitpay.com> | 2014-03-12 11:35:45 -0400 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2014-03-12 15:36:12 +0000 |
| commit | f52ba47e7de16f2c3517f3b76b70b48eabed5fe1 (patch) | |
| tree | 78fe1cd62170313deb2e06028bf7ee159bf3edcd | |
| parent | 34afcb02b4c19687b494b935c3323890427e5dfb (diff) | |
| download | pi-bitcoindev-f52ba47e7de16f2c3517f3b76b70b48eabed5fe1.tar.gz pi-bitcoindev-f52ba47e7de16f2c3517f3b76b70b48eabed5fe1.zip | |
Re: [Bitcoin-development] Multisign payment protocol?
| -rw-r--r-- | 24/fb00512202f30bafcc0a1a9de397003ad2739c | 102 |
1 files changed, 102 insertions, 0 deletions
diff --git a/24/fb00512202f30bafcc0a1a9de397003ad2739c b/24/fb00512202f30bafcc0a1a9de397003ad2739c new file mode 100644 index 000000000..ee0f627fe --- /dev/null +++ b/24/fb00512202f30bafcc0a1a9de397003ad2739c @@ -0,0 +1,102 @@ +Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] + helo=mx.sourceforge.net) + by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <jgarzik@bitpay.com>) id 1WNlCW-0008N8-L0 + for bitcoin-development@lists.sourceforge.net; + Wed, 12 Mar 2014 15:36:12 +0000 +Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com + designates 209.85.212.170 as permitted sender) + client-ip=209.85.212.170; envelope-from=jgarzik@bitpay.com; + helo=mail-wi0-f170.google.com; +Received: from mail-wi0-f170.google.com ([209.85.212.170]) + by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) + (Exim 4.76) id 1WNlCV-0005Pi-KM + for bitcoin-development@lists.sourceforge.net; + Wed, 12 Mar 2014 15:36:12 +0000 +Received: by mail-wi0-f170.google.com with SMTP id n15so2348654wiw.5 + for <bitcoin-development@lists.sourceforge.net>; + Wed, 12 Mar 2014 08:36:05 -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=mq4FirKfBvf+fLRTKHuX1+Dyv1ob9VPL5JYPLQnplEk=; + b=S401YL8E3HJaU/NL4BIY3Wnm+oyt+jxrbiIBPnT9RCkXVBigJjS725OQZMivcWvrDW + V90U4hDSb3EoPcH0Q7HSGStN6A8poBSIEltnW/ROtU/vLWvZaqbCdRS8CVPL9gvoIOOI + fjVJ4jumPxdYH+s2KfPtKk5izLePK+pQl1iSZerV+WId0tDesHv5+cOhQsi9LnruL9ve + VYVX3NTH51lhOkx/FVj+3BAMaAhD7OcEE/Bzv+wUOM5WYUR0hH+31UbuemWUcGrcqYB+ + h4h7tSoaX++BcGEZ79dARGCqxrs2AK9+znbwDtibYkZ9xwcjXZ5P+8dPIRl25+Ex8mbE + Sfuw== +X-Gm-Message-State: ALoCoQmzK4dCqE4YsC3cuS8qWKJ9PMxcbXGdb1Xag3KLpq4bgX9VugIlbNKhYDVxke2xw5E+TBth +X-Received: by 10.194.118.163 with SMTP id kn3mr1854480wjb.77.1394638565321; + Wed, 12 Mar 2014 08:36:05 -0700 (PDT) +MIME-Version: 1.0 +Received: by 10.194.82.197 with HTTP; Wed, 12 Mar 2014 08:35:45 -0700 (PDT) +In-Reply-To: <53202D51.8010008@plan99.net> +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> +From: Jeff Garzik <jgarzik@bitpay.com> +Date: Wed, 12 Mar 2014 11:35:45 -0400 +Message-ID: <CAJHLa0OuXyEz6gcq_dQKmGjJQf3cJjFyzjb38RCB3E6-wMLJ0g@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: 1WNlCV-0005Pi-KM +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 15:36:12 -0000 + +On Wed, Mar 12, 2014 at 5:48 AM, Mike Hearn <mike@plan99.net> wrote: +> CoinVault is also using a partially signed transaction format whereby +> 0-length placeholders are used for missing signatures in the transaction +> scripts. +> +> I don't know how you are implementing this/what framework you're using, but +> I suggest using placeholders that are the length of an actual expected +> signature, at least when forming the transaction. This is what bitcoinj will +> do because otherwise you could end up miscalculating the fee, which is based +> on the final size. See TransactionSignature.dummy() in the API. + +The zero-length placeholder is not a new invention. + +This is what bitcoind produces and expects by default, for a partially +signed transaction. + +-- +Jeff Garzik +Bitcoin core developer and open source evangelist +BitPay, Inc. https://bitpay.com/ + + |