public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Pavol Rusnak <stick@satoshilabs.com>
To: Jonas Schnelli <dev@jonasschnelli.ch>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bip44 extension for P2SH/P2WSH/...
Date: Sat, 14 May 2016 16:07:18 +0200	[thread overview]
Message-ID: <57373116.90902@satoshilabs.com> (raw)
In-Reply-To: <5736DEEA.5030603@jonasschnelli.ch>


[-- Attachment #1.1: Type: text/plain, Size: 335 bytes --]

On 14/05/16 10:16, Jonas Schnelli via bitcoin-dev wrote:
> Importing a bip32 wallet (bip44 or not) is still an expert job IMO.

That's simply not true. All reasonable wallets (reasonable = user
oriented) now use BIP39 mnemonic for doing exactly this.

-- 
Best Regards / S pozdravom,

Pavol "stick" Rusnak
SatoshiLabs.com


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2016-05-14 14:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-13 13:16 [bitcoin-dev] Bip44 extension for P2SH/P2WSH/ Daniel Weigl
2016-05-13 15:00 ` Pavol Rusnak
2016-05-13 16:03   ` Aaron Voisine
2016-05-13 16:11     ` Pavol Rusnak
2016-05-13 16:59       ` Aaron Voisine
2016-05-13 17:57         ` Pavol Rusnak
2016-05-13 21:42           ` Aaron Voisine
2016-05-14  8:16             ` Jonas Schnelli
2016-05-14 12:26               ` Jochen Hoenicke
2016-05-14 14:07               ` Pavol Rusnak [this message]
2016-05-14 16:14                 ` Jonas Schnelli
2016-05-14 17:37                   ` Kenneth Heutmaker
2016-05-15  8:53                   ` Thomas Voegtlin
2016-05-15 10:04                   ` Pavol Rusnak
2016-05-15 12:08     ` Daniel Weigl
2016-05-15 17:36       ` Aaron Voisine
2016-05-14  7:00 ` Andreas Schildbach
2016-05-14 14:08   ` Pavol Rusnak
2016-05-14 17:09     ` Aaron Voisine
2016-05-14 12:15 ` Jochen Hoenicke

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=57373116.90902@satoshilabs.com \
    --to=stick@satoshilabs.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=dev@jonasschnelli.ch \
    /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