diff options
author | Pieter Wuille <pieter.wuille@gmail.com> | 2014-04-08 15:53:52 +0200 |
---|---|---|
committer | bitcoindev <bitcoindev@gnusha.org> | 2014-04-08 13:53:59 +0000 |
commit | df2f29ffc4ff1f0ca32849718e19b7e08b973e8b (patch) | |
tree | 9284397c290dd42bc662373615566eb806241b4e | |
parent | 843f42e9764614040b0fe5f2455f33f6b2ec90f4 (diff) | |
download | pi-bitcoindev-df2f29ffc4ff1f0ca32849718e19b7e08b973e8b.tar.gz pi-bitcoindev-df2f29ffc4ff1f0ca32849718e19b7e08b973e8b.zip |
Re: [Bitcoin-development] New BIP32 structure
-rw-r--r-- | b5/d36b467738e6c589402bd4f7c07231091c9333 | 123 |
1 files changed, 123 insertions, 0 deletions
diff --git a/b5/d36b467738e6c589402bd4f7c07231091c9333 b/b5/d36b467738e6c589402bd4f7c07231091c9333 new file mode 100644 index 000000000..6141000df --- /dev/null +++ b/b5/d36b467738e6c589402bd4f7c07231091c9333 @@ -0,0 +1,123 @@ +Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] + helo=mx.sourceforge.net) + by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <pieter.wuille@gmail.com>) id 1WXWTP-0000mq-GD + for bitcoin-development@lists.sourceforge.net; + Tue, 08 Apr 2014 13:53:59 +0000 +Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com + designates 209.85.223.176 as permitted sender) + client-ip=209.85.223.176; envelope-from=pieter.wuille@gmail.com; + helo=mail-ie0-f176.google.com; +Received: from mail-ie0-f176.google.com ([209.85.223.176]) + by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) + (Exim 4.76) id 1WXWTN-0004Od-PC + for bitcoin-development@lists.sourceforge.net; + Tue, 08 Apr 2014 13:53:59 +0000 +Received: by mail-ie0-f176.google.com with SMTP id rd18so917591iec.35 + for <bitcoin-development@lists.sourceforge.net>; + Tue, 08 Apr 2014 06:53:52 -0700 (PDT) +MIME-Version: 1.0 +X-Received: by 10.50.43.170 with SMTP id x10mr4305882igl.20.1396965232391; + Tue, 08 Apr 2014 06:53:52 -0700 (PDT) +Received: by 10.50.141.135 with HTTP; Tue, 8 Apr 2014 06:53:52 -0700 (PDT) +In-Reply-To: <CAJna-HgfpyHX_0AHwt1Hkj0qhD_-xOcpxsZ9KXq=7CPgwse1hA@mail.gmail.com> +References: <CANEZrP2hbBVGqytmXR1rAcVama4ONnR586Se-Ch=dsxOzy2O4w@mail.gmail.com> + <F2C8C044-EF92-4CCE-9235-28CA7FCE3526@bitsofproof.com> + <CAJHLa0PPAsBLgsy0vgPpUp=UzeR_fWUEzFb5+xtmODEk4MGPVQ@mail.gmail.com> + <CAJfRnm7V6fgcj=TMfa2ZTYWOKtE5aoUT1xnVtKUSyriB=6cagQ@mail.gmail.com> + <CAPg+sBjwf1TcK1CGKVKFzYbV-78j8t-pav7=PEgG7Yqi6-yE7A@mail.gmail.com> + <53344FF8.7030204@gk2.sk> + <CAPg+sBhbx5vy_hewAkFPaiXHzSMNH0qLhEYGjPmQMjR5StP-tw@mail.gmail.com> + <CAJna-Hi0JnrF2_rUx0rGkdnsuCoaD01e3Gobpn+QqbL=D1Uivg@mail.gmail.com> + <CAJna-HirtsGLfAhfUf9dAYEGWo6g=o=eAU187c2pdW8vDFGkPw@mail.gmail.com> + <CAPg+sBg8wDH9yTUoyhRbuzVtbD8hGxya8tOnV4pMToHy3gLrzw@mail.gmail.com> + <CAJna-HiN_1KQmpDJFFX6mGvM63RC0xwXxvfuorpihnzYf4=fsQ@mail.gmail.com> + <CAJna-HgfpyHX_0AHwt1Hkj0qhD_-xOcpxsZ9KXq=7CPgwse1hA@mail.gmail.com> +Date: Tue, 8 Apr 2014 15:53:52 +0200 +Message-ID: <CAPg+sBguSQ8dk1xXKinX+ez4BmdM3sz-huruuhD6NCTsp0kRBQ@mail.gmail.com> +From: Pieter Wuille <pieter.wuille@gmail.com> +To: slush <slush@centrum.cz> +Content-Type: text/plain; charset=ISO-8859-1 +X-Spam-Score: -1.6 (-) +X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. + See http://spamassassin.org/tag/ for more details. + -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for + sender-domain + 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider + (pieter.wuille[at]gmail.com) + -0.0 SPF_PASS SPF: sender matches SPF record + -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from + author's domain + 0.1 DKIM_SIGNED Message has a DKIM or DK signature, + not necessarily valid + -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature +X-Headers-End: 1WXWTN-0004Od-PC +Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> +Subject: Re: [Bitcoin-development] New BIP32 structure +X-BeenThere: bitcoin-development@lists.sourceforge.net +X-Mailman-Version: 2.1.9 +Precedence: list +List-Id: <bitcoin-development.lists.sourceforge.net> +List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> +List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> +List-Post: <mailto:bitcoin-development@lists.sourceforge.net> +List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> +List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> +X-List-Received-Date: Tue, 08 Apr 2014 13:53:59 -0000 + +I see the cause of our disagreement now. + +You actually want to share a single BIP32 tree across different +currency types, but do it in a way that guarantees that they never use +the same keys. + +I would have expected that different chains would use independent +chains, and have serializations encode which chain they belong to. + +Let me offer an alternative suggestion, which is compatible with the +original default BIP32 structure: +* You can use one seed across different chains, but the master nodes +are separate. +* To derive the master node from the seed, the key string "Bitcoin +seed" is replaced by something chain-specific. +* Every encoded node (including master nodes) has a chain-specific +serialization magic. + +This is in practice almost the same as your suggestion, except that +the m/cointype' in m/cointype'/account'/change/n is replaced by +different masters. The only disadvantage I see is that you do not have +a way to encode the "super master" that is the parent of all +chain-specific masters. You can - and with the same security +properties - encode the seed, though. + +-- +Pieter + + +On Tue, Apr 8, 2014 at 3:43 PM, slush <slush@centrum.cz> wrote: +> tl;dr; +> +> It is dangerous to expect that other seed than "xprv" does not contain +> bitcoins or that "xprv" contains only bitcoins, because technically are both +> situations possible. It is still safer to do the lookup; the magic itself is +> ambiguous. +> +> Marek +> +> On Tue, Apr 8, 2014 at 3:40 PM, slush <slush@centrum.cz> wrote: +>> +>> +>> Serialization magic of bip32 seed is in my opinion completely unnecessary. +>> Most of software does not care about it anyway; You can use xprv/xpub pair +>> for main net, testnet, litecoin, dogecoin, whatevercoin. +>> +>> Instead using the same seed (xprv) and then separate the chains *inside* +>> the bip32 path seems more useful to me. +>> +>> Marek +> +> + + |