From: Daniel Weigl <Daniel.Weigl@mycelium•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] [cont'd] Derivation scheme for P2WPKH-nested-in-P2SH based accounts
Date: Wed, 7 Sep 2016 11:42:24 +0200 [thread overview]
Message-ID: <516ecb1e-d8a8-719d-629b-59af808c1b6b@mycelium.com> (raw)
In-Reply-To: <5760259B.7040409@mycelium.com>
Hello again,
sorry, got a bit derailed on that proposal.
But now I think its time to work on it again.
- Any objections to get a BIP-number for it?
If not, can I get one, so I can finish up the test vectors.
Current version: https://github.com/DanielWeigl/bips/blob/master/bip-p2sh-accounts.mediawiki
- I decided against extending it for future P2WPKH addresses
I think that should be a separate account on its own, to reduce implementation work
for future wallets, that only want/need to implement P2WPKH accounts. And to keep it simple.
Was someone working on the P2WPKH address format in the meantime? (ie. alternative for [2])
- We will also need a extension to the BIP32 serialization format[1]
It should be possible to export/import a xPriv/xPub key across compatible wallets, and they
should be able without guesswork, fuzzy checks or asking the user to import the correct account type.
Thinking about some flexible tag-based backwards compatible extensions - but thats a different BIP in itself.
Cheers,
Daniel
[1] https://github.com/DanielWeigl/bips/blob/master/bip-0032.mediawiki#Serialization_format
[2] https://github.com/bitcoin/bips/blob/master/bip-0142.mediawiki
On 2016-06-14 17:41, Daniel Weigl via bitcoin-dev wrote:
> 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
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
prev parent reply other threads:[~2016-09-07 10:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 15:41 [bitcoin-dev] RFC for BIP: " Daniel Weigl
2016-06-15 10:26 ` 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 ` Daniel Weigl [this message]
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=516ecb1e-d8a8-719d-629b-59af808c1b6b@mycelium.com \
--to=daniel.weigl@mycelium$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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