public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: slush <slush@centrum.cz>
To: Jim <jim618@fastmail.co.uk>
Cc: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Roadmap to getting users onto SPV clients
Date: Tue, 4 Dec 2012 22:23:59 +0000	[thread overview]
Message-ID: <CAJna-HjuHMDr4sO7FRGGfhncvQsUXygRp6v1D_BVbbZ+3zmcSQ@mail.gmail.com> (raw)
In-Reply-To: <1354650998.21742.140661161849669.1371855A@webmail.messagingengine.com>

[-- Attachment #1: Type: text/plain, Size: 807 bytes --]

Jim, perfect idea with some logo indicating wallet compatibility! This
should cover BIP32 + some mnemonic algorithm for easy transferring of
wallets across various clients.

Btw I asked ThomasV for making BIP from his mnemonic algorithm and he
agreed, so I believe some proposal will be here pretty soon.

slush

On Tue, Dec 4, 2012 at 7:56 PM, Jim <jim618@fastmail.co.uk> wrote:
>
> Also, as BIP32 support is added to clients and codebases then the actual
> variant of software to use to access your wallet will become relatively
> less important. Combined with a standardised seed -> passphrase
> algorithm the user can just type in their long passphrase into any BIP32
> compliant software and click/ buzz/ whirr : there is their wallet. We
> should have a little logo for HD wallet compliance ! :-)
>
>

[-- Attachment #2: Type: text/html, Size: 1239 bytes --]

  reply	other threads:[~2012-12-04 22:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.70419.1354648162.2176.bitcoin-development@lists.sourceforge.net>
2012-12-04 19:56 ` [Bitcoin-development] Roadmap to getting users onto SPV clients Jim
2012-12-04 22:23   ` slush [this message]
2012-12-04 17:46 Mike Hearn
2012-12-04 18:03 ` Alan Reiner
2012-12-04 18:08 ` Will
2012-12-04 18:17 ` Gregory Maxwell
2012-12-04 20:58   ` Mike Hearn
2012-12-04 21:41     ` Gregory Maxwell
2012-12-04 22:44       ` Alan Reiner
2012-12-05  0:27         ` Gregory Maxwell
2012-12-05  2:08           ` Alan Reiner
2012-12-05  2:54             ` Gregory Maxwell
2012-12-05  5:38               ` Jim Nguyen
2012-12-05  7:50                 ` Wladimir
2012-12-05  9:43                   ` Gary Rowe
2012-12-05 10:19                     ` Robert Backhaus
2012-12-05 10:43               ` Mike Hearn
2012-12-04 18:57 ` Mark Friedenbach
2012-12-04 19:36   ` Gregory Maxwell

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=CAJna-HjuHMDr4sO7FRGGfhncvQsUXygRp6v1D_BVbbZ+3zmcSQ@mail.gmail.com \
    --to=slush@centrum.cz \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=jim618@fastmail.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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