From: Thomas Voegtlin <thomasv@electrum.org>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP proposal for Lightning-oriented multiaccount multisig HD wallets
Date: Wed, 30 Aug 2017 12:07:24 +0200 [thread overview]
Message-ID: <cb022f27-93ce-b61d-097b-8ccc2ef3e288@electrum.org> (raw)
In-Reply-To: <8088fa79-8e77-8663-afb4-800a405a6182@chainside.net>
On 29.08.2017 12:19, Simone Bronzini via bitcoin-dev wrote:
> 2. SegWit addresses:
> since mixing SegWit and non-SegWit addresses on the same BIP44 structure
> could lead to UTXOs not being completely recognised by old wallets,
> BIP49 was proposed to separate the key space.
This will lead to old UTXOs not being recognized by NEW wallets, because
at some point new wallets will not care about implementing old standards.
The only way to address this is to get out of bip39 and bip43, and to
include a version number in the mnemonic seed.
next prev parent reply other threads:[~2017-08-30 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 10:19 [bitcoin-dev] BIP proposal for Lightning-oriented multiaccount multisig HD wallets Simone Bronzini
2017-08-29 20:07 ` Luke Dashjr
2017-08-30 12:22 ` Simone Bronzini
2017-08-30 10:07 ` Thomas Voegtlin [this message]
2017-08-30 12:48 ` Simone Bronzini
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=cb022f27-93ce-b61d-097b-8ccc2ef3e288@electrum.org \
--to=thomasv@electrum.org \
--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