Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WNNvL-0005rz-Mv for bitcoin-development@lists.sourceforge.net; Tue, 11 Mar 2014 14:44:55 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com designates 209.85.212.174 as permitted sender) client-ip=209.85.212.174; envelope-from=jgarzik@bitpay.com; helo=mail-wi0-f174.google.com; Received: from mail-wi0-f174.google.com ([209.85.212.174]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WNNvK-0004FO-NH for bitcoin-development@lists.sourceforge.net; Tue, 11 Mar 2014 14:44:55 +0000 Received: by mail-wi0-f174.google.com with SMTP id d1so992410wiv.1 for ; Tue, 11 Mar 2014 07:44:48 -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:content-type; bh=Et0Im6UyldkfeXSGFVv4MCowxhEx9YuhAmni52cId1M=; b=WOocR9zSvkTXKbk6Fpv+Rgbraknu0VaKs2jkjoTZ+gGWgtdzVL6gFuCcR1k6CR8rh2 g+AZOhdoSpve2IG3fhnrsGvfm20/FgkHGiDbk1ndtTb4Hsh5QMWglxU36a+de+DuYiKr YFhXxOVzsv7rEFhEos3GGSGd884rJc3bAmHKE6WJhXQyUDkEEVb6OK1Rn63VIPn+Ubt5 HffDM4Qr9Vf5MVqAxfPxWocj47jiomIL8buon4GsbZTp+G8LIDAkmuF4keVgySN3j11o lkb0ZynG1c9sgsati98cJV82d6p2a1qJ66fneVNiGsN4OvV4APKyZg7JdlUKmzLIXbXK hh6Q== X-Gm-Message-State: ALoCoQm2T2iHT+WG649Dr+hznlVmMHpeCyRaO9TwgbnUhFUIdwYfofgdZLQuSldHvxt7zMvO69Tw X-Received: by 10.181.13.112 with SMTP id ex16mr3468806wid.23.1394549088539; Tue, 11 Mar 2014 07:44:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.82.197 with HTTP; Tue, 11 Mar 2014 07:44:28 -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 10:44:28 -0400 Message-ID: To: Bitcoin Dev 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: 1WNNvK-0004FO-NH 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 14:44:55 -0000 (#include ) Right now, HD is hot air. Let us end the pie-in-the-sky assumptions about how HD will save the day, with zero code to back it up. Bitcoin Wallet purportedly fails to rotate addresses, a privacy ugly, because of this Waiting For Godot situation. An attempt to add a simple, stateless RPC stalled because we are all Waiting For Godot, also: https://github.com/bitcoin/bitcoin/pull/3520 Until the major user wallets and bitcoind have -basic- HD support, it is premature to build anything on top of HD. We really have no clue at this juncture how difficult will be the HD rollout. -- Jeff Garzik Bitcoin core developer and open source evangelist BitPay, Inc. https://bitpay.com/