From: Daniel Weigl <Daniel.Weigl@mycelium.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] RFC for BIP: Derivation scheme for P2WPKH-nested-in-P2SH based accounts
Date: Tue, 14 Jun 2016 17:41:15 +0200 [thread overview]
Message-ID: <5760259B.7040409@mycelium.com> (raw)
Hi List,
Following up to the discussion last month ( https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-May/012695.html ), ive prepared a proposal for a BIP here:
https://github.com/DanielWeigl/bips/blob/master/bip-p2sh-accounts.mediawiki
Any comments on it? Does anyone working on a BIP44 compliant wallet implement something different?
If there are no objection, id also like to request a number for it.
Thx,
Daniel
next reply other threads:[~2016-06-14 15:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 15:41 Daniel Weigl [this message]
2016-06-15 10:26 ` [bitcoin-dev] RFC for BIP: Derivation scheme for P2WPKH-nested-in-P2SH based accounts Jochen Hoenicke
2016-06-15 10:53 ` Daniel Weigl
2016-06-15 11:00 ` Pieter Wuille
2016-06-15 17:08 ` Russell O'Connor
2016-06-18 6:07 ` Aaron Voisine
2016-09-07 9:42 ` [bitcoin-dev] [cont'd] " Daniel Weigl
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=5760259B.7040409@mycelium.com \
--to=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