From: Kabuto Samourai <kabuto@samouraiwallet.com>
To: Pavol Rusnak <stick@satoshilabs.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Proposal: Extended serialization format for BIP-32 wallets
Date: Thu, 7 Sep 2017 11:33:09 -0500 [thread overview]
Message-ID: <CA+_kfXLjeQJbJGy5=ssynGOTaGkzvzWQ2RMdhcqCG1DNjqvFWA@mail.gmail.com> (raw)
In-Reply-To: <84f4a4b8-fcbd-433b-9556-174ec5475f61@satoshilabs.com>
[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]
OutputType byte solution is nearly equivalent to {x,y,z} and adds redundant
data. Implementations could erroneously (maliciously) assign the wrong
output type for the given purpose field.
We could reduce the scope of this improvement to BIP43, as suggested by
Thomas. BIP32-generic wallets may implement something else.
On Thu, Sep 7, 2017 at 11:23 AM, Pavol Rusnak via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> On 07/09/17 06:29, Thomas Voegtlin via bitcoin-dev wrote:
> > A solution is still needed to wallets who do not wish to use BIP43
>
> What if we added another byte field OutputType for wallets that do not
> follow BIP43?
>
> 0x00 - P2PKH output type
> 0x01 - P2WPKH-in-P2SH output type
> 0x02 - native Segwit output type
>
> Would that work for you?
>
> The question is whether this field should be present only if depth==0x00
> or at all times. What is your suggestion, Thomas?
>
> --
> Best Regards / S pozdravom,
>
> Pavol "stick" Rusnak
> CTO, SatoshiLabs
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--
-Kabuto
PGP Fingerprint: 1A83 4A96 EDE7 E286 2C5A B065 320F B934 A79B 6A99
[-- Attachment #2: Type: text/html, Size: 2187 bytes --]
next prev parent reply other threads:[~2017-09-07 16:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 22:29 [bitcoin-dev] Proposal: Extended serialization format for BIP-32 wallets Pavol Rusnak
2017-09-07 3:52 ` Kabuto Samourai
2017-09-07 16:25 ` Pavol Rusnak
2017-09-07 16:30 ` Kabuto Samourai
2017-09-07 16:37 ` Pavol Rusnak
2017-09-07 18:02 ` Peter Todd
2017-09-07 4:29 ` Thomas Voegtlin
2017-09-07 16:23 ` Pavol Rusnak
2017-09-07 16:33 ` Kabuto Samourai [this message]
2017-09-07 19:35 ` Andreas Schildbach
2017-09-07 20:00 ` Pavol Rusnak
2017-09-07 20:39 ` Thomas Voegtlin
2017-09-07 16:47 ` Jonas Schnelli
2017-09-07 18:09 ` Peter Todd
2017-09-07 18:38 ` Pavol Rusnak
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='CA+_kfXLjeQJbJGy5=ssynGOTaGkzvzWQ2RMdhcqCG1DNjqvFWA@mail.gmail.com' \
--to=kabuto@samouraiwallet.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=stick@satoshilabs.com \
/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