<div dir="ltr">William,<br><br>I believe the reasoning for this is stated in the Coin Type section.<br><br>"Public derivation is used so that cosigners need only know one of each other's public keys, rather than needing to distribute public keys for each coin."<br><br>BIP44 has a coin level, but it's a private derived level, so cosigners would not be able to generate multiple crypto currencies of each others' without giving each other n xpubs where n is the number of currencies shared. This new proposal basically sticks coin type on the public derivation side of things so that I could generate litecoin or darkcoin multisigs without your permission...<br><br>Kefkius,<br><br>This BIP seems like a good fit for multi-currency wallets based on multisig. So kudos for putting it in writing.<br><br>However, I don't know if this is really a BIP thing. It's not improving Bitcoin (Bitcoin Improvement Proposal... remember?), in fact, by definition it is improving altcoin usability.<br><br>For that reason alone I will say I disagree for a BIP for this.<br>- Jona<div><br><br>2015-04-08 16:46 GMT+09:00 William Swanson <<a href="mailto:swansontec@gmail.com">swansontec@gmail.com</a>>:<br>><br>> It's not really clear why this is better than BIP 44 as it already<br>> stands. You have the same fields, but they are just in a different<br>> order. Couldn't you just use the existing BIP 44 hierarchy, but add<br>> the convention that "wallet/account N" is the same wallet in each<br>> supported currency?<br>><br>> For example, if I have a wallet called "business expenses", which<br>> happens to be wallet m / 44' / 0' / 5', for Bitcoin, then the same<br>> wallet would be m / 44' / 3' / 5' for Dogecoin, and m / 44' / 2' / 5'<br>> for Litecoin.<br>><br>> I am trying to think of examples where your proposal is better than<br>> BIP 44, but I can't think of any. Even backup recovery works fine. I<br>> assume that your idea is to continue iterating over the different<br>> wallet indices as long as you are finding funds in *any* currency.<br>> Well, you can still do that with BIP 44. The fields are in a different<br>> order, but that doesn't affect the algorithm in any way.<br>><br>> Maybe you have some deeper insight I'm not seeing, but if so, you need<br>> to clearly explain that in your motivation section. The current<br>> explanation, "This limits the possible implementations of<br>> multi-currency, multisignature wallets," is pretty vauge. Also, there<br>> is nothing in this spec that addresses the multisignature use-case.<br>> The BIP 45 spec does a lot of extra work to make multisignature work<br>> smoothly.<br>><br>> I'm not trying to criticize your proposal. I'm just trying to<br>> understand what it's trying to accomplish.<br>><br>> -William Swanson<br>><br>><br>> On Wed, Apr 8, 2015 at 12:05 AM, Kefkius <kefkius@maza.club> wrote:<br>> > I have a potential BIP, "Multi-Currency Hierarchy For Use In<br>> > Multisignature Deterministic Wallets." I'm requesting discussion on it,<br>> > and possibly assignment of a BIP number.<br>> ><br>> > It's located in this github gist:<br>> > <a href="https://gist.github.com/Kefkius/1aa02945e532f8739023">https://gist.github.com/Kefkius/1aa02945e532f8739023</a><br>> ><br>> > ------------------------------------------------------------------------------<br>> > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT<br>> > Develop your own process in accordance with the BPMN 2 standard<br>> > Learn Process modeling best practices with Bonita BPM through live exercises<br>> > <a href="http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-">http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-</a> event?utm_<br>> > source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF<br>> > _______________________________________________<br>> > Bitcoin-development mailing list<br>> > <a href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a><br>> > <a href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a><br>><br>> ------------------------------------------------------------------------------<br>> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT<br>> Develop your own process in accordance with the BPMN 2 standard<br>> Learn Process modeling best practices with Bonita BPM through live exercises<br>> <a href="http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-">http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-</a> event?utm_<br>> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF<br>> _______________________________________________<br>> Bitcoin-development mailing list<br>> <a href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a><br>> <a href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a><br><br><br><br><br>--<br>-----BEGIN PGP PUBLIC KEY BLOCK-----<br>Comment: <a href="http://openpgpjs.org">http://openpgpjs.org</a><br><br>xsBNBFTmJ8oBB/9rd+7XLxZG/x/KnhkVK2WBG8ySx91fs+qQfHIK1JrakSV3<br>x6x0cK3XLClASLLDomm7Od3Q/fMFzdwCEqj6z60T8wgKxsjWYSGL3mq8ucdv<br>iBjC3wGauk5dQKtT7tkCFyQQbX/uMsBM4ccGBICoDmIJlwJIj7fAZVqGxGOM<br>bO1RhYb4dbQA2qxYP7wSsHJ6/ZNAXyEphOj6blUzdqO0exAbCOZWWF+E/1SC<br>EuKO4RmL7Imdep7uc2Qze1UpJCZx7ASHl2IZ4UD0G3Qr3pI6/jvNlaqCTa3U<br>3/YeJwEubFsd0AVy0zs809RcKKgX3W1q+hVDTeWinem9RiOG/vT+Eec/ABEB<br>AAHNI2tpbm9zaGl0YSA8a2lub3NoaXRham9uYUBnbWFpbC5jb20+wsByBBAB<br>CAAmBQJU5ifRBgsJCAcDAgkQRB9iZ30dlisEFQgCCgMWAgECGwMCHgEAAC6Z<br>B/9otobf0ASHYdlUBeIPXdDopyjQhR2RiZGYaS0VZ5zzHYLDDMW6ZIYm5CjO<br>Fc09ETLGKFxH2RcCOK2dzwz+KRU4xqOrt/l5gyd50cFE1nOhUN9+/XaPgrou<br>WhyT9xLeGit7Xqhht93z2+VanTtJAG6lWbAZLIZAMGMuLX6sJDCO0GiO5zxa<br>02Q2D3kh5GL57A5+oVOna12JBRaIA5eBGKVCp3KToT/z48pxBe3WAmLo0zXr<br>hEgTSzssfb2zTwtB3Ogoedj+cU2bHJvJ8upS/jMr3TcdguySmxJlGpocVC/e<br>qxq12Njv+LiETOrD8atGmXCnA+nFNljBkz+l6ADl93jHzsBNBFTmJ9EBCACu<br>Qq9ZnP+aLU/Rt6clAfiHfTFBsJvLKsdIKeE6qHzsU1E7A7bGQKTtLEnhCCQE<br>W+OQP+sgbOWowIdH9PpwLJ3Op+NhvLlMxRvbT36LwCmBL0yD7bMqxxmmVj8n<br>vlMMRSe4wDSIG19Oy7701imnHZPm/pnPlneg/Meu/UffpcDWYBbAFX8nrXPY<br>vkVULcI/qTcCxW/+S9fwoXjQhWHaiJJ6y3cYOSitN31W9zgcMvLwLX3JgDxE<br>flkwq/M+ZkfCYnS3GAPEt8GkVKy2eHtCJuNkGFlCAmKMX0yWzHRAkqOMN5KP<br>LFbkKY2GQl13ztWp82QYJZpj5af6dmyUosurn6AZABEBAAHCwF8EGAEIABMF<br>AlTmJ9QJEEQfYmd9HZYrAhsMAABKbgf/Ulu5JAk4fXgH0DtkMmdkFiKEFdkW<br>0Wkw7Vhd5eZ4NzeP9kOkD01OGweT9hqzwhfT2CNXCGxh4UnvEM1ZMFypIKdq<br>0XpLLJMrDOQO021UjAa56vHZPAVmAM01z5VzHJ7ekjgwrgMLmVkm0jWKEKaO<br>n/MW7CyphG7QcZ6cJX2f6uJcekBlZRw9TNYRnojMjkutlOVhYJ3J78nc/k0p<br>kcgV63GB6D7wHRF4TVe4xIBqKpbBhhN+ISwFN1z+gx3lfyRMSmiTSrGdKEQe<br>XSIQKG8XZQZUDhLNkqPS+7EMV1g7+lOfT4GhLL68dUXDa1e9YxGH6zkpVECw<br>Spe3vsHZr6CqFg==<br>=/vUJ<br>-----END PGP PUBLIC KEY BLOCK-----<br><div class="gmail_extra">
</div></div></div>