From: Pavol Rusnak <stick@satoshilabs.com>
To: Daniel Weigl <Daniel.Weigl@mycelium.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bip44 extension for P2SH/P2WSH/...
Date: Fri, 13 May 2016 17:00:39 +0200 [thread overview]
Message-ID: <5735EC17.5040901@satoshilabs.com> (raw)
In-Reply-To: <5735D3A4.7090608@mycelium.com>
On 13/05/16 15:16, Daniel Weigl via bitcoin-dev wrote:
> 2) Define a new derivation path, parallel to Bip44, but a different 'purpose' (eg. <BipNumber-of-this-BIP>' instead of 44'). Let the user choose which account he want to add ("Normal account", "Witness account").
We had quite a long discussion in our team some time ago and we agreed
on that option #2 is much better and we'd like to implement this way in
myTREZOR.
> +) Wallet needs only to take care of 1 address per public key
True, if this BIP only supports P2WPKH.
P2WSH should probably be handled by another account type and another
BIP, anyway.
> Has any Bip44 compliant wallet already done any integration at this point?
We have something in the pipeline, but no visible results yet.
--
Best Regards / S pozdravom,
Pavol "stick" Rusnak
SatoshiLabs.com
next prev parent reply other threads:[~2016-05-13 15:00 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 [this message]
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
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=5735EC17.5040901@satoshilabs.com \
--to=stick@satoshilabs.com \
--cc=Daniel.Weigl@mycelium.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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