Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WNLxq-00010E-HB for bitcoin-development@lists.sourceforge.net; Tue, 11 Mar 2014 12:39:22 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com designates 74.125.82.42 as permitted sender) client-ip=74.125.82.42; envelope-from=jgarzik@bitpay.com; helo=mail-wg0-f42.google.com; Received: from mail-wg0-f42.google.com ([74.125.82.42]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WNLxp-0007jN-Kd for bitcoin-development@lists.sourceforge.net; Tue, 11 Mar 2014 12:39:22 +0000 Received: by mail-wg0-f42.google.com with SMTP id y10so9939629wgg.1 for ; Tue, 11 Mar 2014 05:39:15 -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=2Wd44ES+qbLAYvIyft6xp43M+fLLnMLriZT6njyf3jo=; b=bhnMasBsZe47Gjm+lTJ+UXiRZszzqWerBAp1FXek6Kx47VHrMiDwb69KrBIlherX4D h0IFRnBINt1Hdpeuw6FrySM9lfO8g7EEs/Cc45fRzy2w0BreQtJaCvdFqT0Ig0loqJLX bB87yo8cERl+XQs2hMc7ubq6tvb72xJTicO1J+v7B1DIBt9PcVHXueCkL/vR8IUOFi4j pQXriOjmP2j8TL3nIUM3NdMmTdsw0Ag12VWnBr+yxs6rzkqp6wy+U+nEKARZ3H70VHoR A6MwPGtzxEwQx1neemVtkp0j0wQo2mqWrbd+gVRjeQRHQhKk131qXIm1ogL20LPNC7s/ QQNw== X-Gm-Message-State: ALoCoQm0PJDGDayxmlJX0pKjnU8+cJIhhBCEfycC1L4Fi1jTgcglu7a47NEDEIOX8cM44CpvXvt6 X-Received: by 10.180.87.162 with SMTP id az2mr2877768wib.23.1394541555509; Tue, 11 Mar 2014 05:39:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.82.197 with HTTP; Tue, 11 Mar 2014 05:38:55 -0700 (PDT) In-Reply-To: References: <531DFDF8.80008@gmail.com> <531E52FE.5090107@jerviss.org> <531E5454.1030601@gmail.com> From: Jeff Garzik Date: Tue, 11 Mar 2014 08:38:55 -0400 Message-ID: To: Drak 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: 1WNLxp-0007jN-Kd Cc: kjj , Bitcoin Dev 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 12:39:22 -0000 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. -- Jeff Garzik Bitcoin core developer and open source evangelist BitPay, Inc. https://bitpay.com/