public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Simone Bronzini <simone.bronzini@chainside.net>
To: Thomas Voegtlin <thomasv@electrum.org>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP proposal for Lightning-oriented multiaccount multisig HD wallets
Date: Wed, 30 Aug 2017 14:48:24 +0200	[thread overview]
Message-ID: <2568a65f-3dad-315f-3959-cea6048ab9ba@chainside.net> (raw)
In-Reply-To: <cb022f27-93ce-b61d-097b-8ccc2ef3e288@electrum.org>


[-- Attachment #1.1.1: Type: text/plain, Size: 1375 bytes --]

> 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.

Your observations make perfect sense. That's exactly why we endorse
option b. in my previous email.

> The only way to address this is to get out of bip39 and bip43, and to
> include a version number in the mnemonic seed.

As for the idea of having a versioning on mnemonic seeds, I believe it
would be a very useful feature indeed. How about opening a new,
separate, topic about it?


On 30/08/17 12:07, Thomas Voegtlin via bitcoin-dev wrote:
>
> 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.
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev


[-- Attachment #1.1.2: 0xB2E60C73.asc --]
[-- Type: application/pgp-keys, Size: 15783 bytes --]

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

      reply	other threads:[~2017-08-30 12:58 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
2017-08-30 12:48   ` Simone Bronzini [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=2568a65f-3dad-315f-3959-cea6048ab9ba@chainside.net \
    --to=simone.bronzini@chainside.net \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=thomasv@electrum.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