From: Jim <jim618@fastmail•co.uk>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] BIP32 "wallet structure" in use? Remove it?
Date: Fri, 25 Apr 2014 15:53:27 +0100 [thread overview]
Message-ID: <1398437607.23028.110362141.03111A2A@webmail.messagingengine.com> (raw)
In-Reply-To: <ljdd29$522$1@ger.gmane.org>
Oh dear.
For reasons that are perfectly reasonable we are close to losing any chance of intra-client HD compatibility for BIP32 wallets.
In the next 12 months there will probably be collectively millions of users of our new wallets. I don't want them to suffer from vendor lockin.
Can we not agree on a lowest common denominator that we agree to support ?
An "HD Basic" if you like.
For entry level users we can keep things simple and any "HD Basic" bitcoin will be fully interoperable.
Sure, if you use anything fancy you'll be locked in to a particular wallet but a lot of users just want somewhere safe to put their bitcoin, spend it and receive it.
I appreciate standising everything is very difficult (if not impossible) but if we don't have a minimum of interoperability I think we'll do our users a disservice.
On Fri, Apr 25, 2014, at 11:23 AM, Andreas Schildbach wrote:
> Does anyone use or plan to use the "wallet structure" part of the BIP32
> document?
>
> I suggest removing it from the document and maybe instead point at
> BIP43. That new specification proposal just defines a "purpose" and
> leaves everything else to the inventor of that purpose. The idea it that
> over time a standard will evolve naturally rather than top-down.
>
> https://github.com/bitcoin/bips/blob/master/bip-0043.mediawiki
>
> I'd volunteer to submit a pull request if I can see some level of
> consent here.
>
>
> ------------------------------------------------------------------------------
> Start Your Social Network Today - Download eXo Platform
> Build your Enterprise Intranet with eXo Platform Software
> Java Based Open Source Intranet - Social, Extensible, Cloud Ready
> Get Started Now And Turn Your Intranet Into A Collaboration Platform
> http://p.sf.net/sfu/ExoPlatform
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
--
http://bitcoin-solutions.co.uk
next prev parent reply other threads:[~2014-04-25 14:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 10:23 Andreas Schildbach
2014-04-25 14:53 ` Jim [this message]
2014-04-25 15:46 ` Gregory Maxwell
2014-04-25 15:49 ` Mike Hearn
2014-04-25 21:58 ` Aaron Voisine
2014-04-26 10:36 ` Thomas Voegtlin
2014-04-26 10:48 ` Tier Nolan
2014-04-26 10:59 ` Tamas Blummer
2014-04-26 11:03 ` Tamas Blummer
2014-04-26 12:24 ` Pavol Rusnak
2014-04-26 13:41 ` Pieter Wuille
2014-04-26 16:03 ` 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=1398437607.23028.110362141.03111A2A@webmail.messagingengine.com \
--to=jim618@fastmail$(echo .)co.uk \
--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