From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WNN5q-0004YG-Ds for bitcoin-development@lists.sourceforge.net; Tue, 11 Mar 2014 13:51:42 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.54 as permitted sender) client-ip=209.85.213.54; envelope-from=gavinandresen@gmail.com; helo=mail-yh0-f54.google.com; Received: from mail-yh0-f54.google.com ([209.85.213.54]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WNN5p-0001RH-Ow for bitcoin-development@lists.sourceforge.net; Tue, 11 Mar 2014 13:51:42 +0000 Received: by mail-yh0-f54.google.com with SMTP id f73so2988833yha.27 for ; Tue, 11 Mar 2014 06:51:36 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.236.80.8 with SMTP id j8mr1093700yhe.151.1394545896254; Tue, 11 Mar 2014 06:51:36 -0700 (PDT) Received: by 10.170.133.195 with HTTP; Tue, 11 Mar 2014 06:51:36 -0700 (PDT) In-Reply-To: References: <531DFDF8.80008@gmail.com> <531E52FE.5090107@jerviss.org> <531E5454.1030601@gmail.com> Date: Tue, 11 Mar 2014 09:51:36 -0400 Message-ID: From: Gavin Andresen To: Jeff Garzik Content-Type: multipart/alternative; boundary=20cf300fb33dc4f50404f4550488 X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gavinandresen[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -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: 1WNN5p-0001RH-Ow Cc: Bitcoin Dev , kjj 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: Tue, 11 Mar 2014 13:51:42 -0000 --20cf300fb33dc4f50404f4550488 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Mar 11, 2014 at 8:38 AM, Jeff Garzik wrote: > On Tue, Mar 11, 2014 at 7:43 AM, Drak wrote: > > I very much like the idea of assuming each party uses HD wallets, that > > certainly simplifies things greatly. > > It also assumes a reality different from our current one. > Multisig wallets are a different reality from our current one, so when we move to that new reality we should do it correctly from the beginning. -- -- Gavin Andrese --20cf300fb33dc4f50404f4550488 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On T= ue, Mar 11, 2014 at 8:38 AM, Jeff Garzik <jgarzik@bitpay.com> wrote:
On Tue, Mar 11, 2014 at 7:43= AM, Drak <drak@zikula.org> wr= ote:
> I very much like the idea of assuming each party uses HD wallets, that=
> certainly simplifies things greatly.

It also assumes a reality different from our current one.

Multisig wallet= s are a different reality from our current one, so when we move to that new= reality we should do it correctly from the beginning.

--
--
Gavin Andrese
--20cf300fb33dc4f50404f4550488--