public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@bitpay•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Multisign payment protocol?
Date: Tue, 11 Mar 2014 10:44:28 -0400	[thread overview]
Message-ID: <CAJHLa0NHKWqXMd23Fr46adGinQmjcLRxyBB-Ra9tJwu4Ein7GA@mail.gmail.com> (raw)
In-Reply-To: <CABsx9T3fKBCFd7d-yP-0WgN2TBwN8Es=hZqxPBnThESKz1jLvA@mail.gmail.com>

(#include <rant.h>)

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/



  parent reply	other threads:[~2014-03-11 14:44 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10 17:39 Drak
2014-03-10 17:49 ` Gavin Andresen
2014-03-10 18:01   ` Alan Reiner
2014-03-11  0:04     ` kjj
2014-03-11  0:09       ` Alan Reiner
2014-03-11  0:14         ` Jeff Garzik
2014-03-11  1:15           ` Gavin Andresen
2014-03-11 11:43             ` Drak
2014-03-11 12:38               ` Jeff Garzik
2014-03-11 13:51                 ` Gavin Andresen
2014-03-11 14:13                   ` Jeff Garzik
2014-03-11 14:23                     ` Gavin Andresen
2014-03-11 14:34                       ` Jeff Garzik
2014-03-11 14:44                       ` Jeff Garzik [this message]
2014-03-11 14:53                         ` Gary Rowe
2014-03-11 15:18                           ` Mike Hearn
2014-03-11 17:11                             ` Miron
2014-03-11 15:37                           ` Thomas Voegtlin
2014-03-11 21:12                     ` Peter Todd
2014-03-11 17:41                   ` Odinn Cyberguerrilla
2014-03-12  0:29                     ` Jean-Pierre Rupp
2014-03-12  2:35                       ` Alan Reiner
2014-03-12  2:48                         ` Eric Lombrozo
2014-03-12  9:48                           ` Mike Hearn
2014-03-12 15:35                             ` Jeff Garzik
2014-03-12 16:02                               ` Mike Hearn
2014-03-12 16:09                                 ` Drak
2014-03-12 16:14                                   ` Mike Hearn
2014-03-12 16:24                                     ` Peter Todd
2014-03-12 16:33                                 ` Jeff Garzik
2014-03-12 16:41                                   ` Mike Hearn
2014-03-12 16:47                                     ` Peter Todd
2014-03-12 16:57                                     ` Jeff Garzik
2014-03-10 17:50 ` Mike Hearn
2014-03-10 18:12 ` Jeff Garzik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJHLa0NHKWqXMd23Fr46adGinQmjcLRxyBB-Ra9tJwu4Ein7GA@mail.gmail.com \
    --to=jgarzik@bitpay$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox