{"type":"rich","version":"1.0","author_name":"npub1ccegg9n9lnx6huppxg43m95488yur7pfemkn3pz0agjws5ffvtts0ex8m8","author_url":"https://nostr.ae/npub1ccegg9n9lnx6huppxg43m95488yur7pfemkn3pz0agjws5ffvtts0ex8m8","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-04-08\n📝 Original message:Pieter,\n\nyour suggestion has charm since “Bitcoin seed” would even not need \na global dictionary like the interpretation of the first level, since it would be self describing.\n\nRegards,\n\nTamas Blummer\nhttp://bitsofproof.com\n\nOn 08.04.2014, at 15:53, Pieter Wuille \u003cpieter.wuille at gmail.com\u003e wrote:\n\n\u003e I see the cause of our disagreement now.\n\u003e \n\u003e You actually want to share a single BIP32 tree across different\n\u003e currency types, but do it in a way that guarantees that they never use\n\u003e the same keys.\n\u003e \n\u003e I would have expected that different chains would use independent\n\u003e chains, and have serializations encode which chain they belong to.\n\u003e \n\u003e Let me offer an alternative suggestion, which is compatible with the\n\u003e original default BIP32 structure:\n\u003e * You can use one seed across different chains, but the master nodes\n\u003e are separate.\n\u003e * To derive the master node from the seed, the key string \"Bitcoin\n\u003e seed\" is replaced by something chain-specific.\n\u003e * Every encoded node (including master nodes) has a chain-specific\n\u003e serialization magic.\n\u003e \n\u003e This is in practice almost the same as your suggestion, except that\n\u003e the m/cointype' in m/cointype'/account'/change/n is replaced by\n\u003e different masters. The only disadvantage I see is that you do not have\n\u003e a way to encode the \"super master\" that is the parent of all\n\u003e chain-specific masters. You can - and with the same security\n\u003e properties - encode the seed, though.\n\u003e \n\u003e -- \n\u003e Pieter\n\u003e \n\u003e \n\u003e On Tue, Apr 8, 2014 at 3:43 PM, slush \u003cslush at centrum.cz\u003e wrote:\n\u003e\u003e tl;dr;\n\u003e\u003e \n\u003e\u003e It is dangerous to expect that other seed than \"xprv\" does not contain\n\u003e\u003e bitcoins or that \"xprv\" contains only bitcoins, because technically are both\n\u003e\u003e situations possible. It is still safer to do the lookup; the magic itself is\n\u003e\u003e ambiguous.\n\u003e\u003e \n\u003e\u003e Marek\n\u003e\u003e \n\u003e\u003e On Tue, Apr 8, 2014 at 3:40 PM, slush \u003cslush at centrum.cz\u003e wrote:\n\u003e\u003e\u003e \n\u003e\u003e\u003e \n\u003e\u003e\u003e Serialization magic of bip32 seed is in my opinion completely unnecessary.\n\u003e\u003e\u003e Most of software does not care about it anyway; You can use xprv/xpub pair\n\u003e\u003e\u003e for main net, testnet, litecoin, dogecoin, whatevercoin.\n\u003e\u003e\u003e \n\u003e\u003e\u003e Instead using the same seed (xprv) and then separate the chains *inside*\n\u003e\u003e\u003e the bip32 path seems more useful to me.\n\u003e\u003e\u003e \n\u003e\u003e\u003e Marek\n\u003e\u003e \n\u003e\u003e \n\u003e \n\u003e ------------------------------------------------------------------------------\n\u003e Put Bad Developers to Shame\n\u003e Dominate Development with Jenkins Continuous Integration\n\u003e Continuously Automate Build, Test \u0026 Deployment \n\u003e Start a new project now. Try Jenkins in the cloud.\n\u003e http://p.sf.net/sfu/13600_Cloudbees\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e \n\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140408/272c6548/attachment.html\u003e\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 495 bytes\nDesc: Message signed with OpenPGP using GPGMail\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140408/272c6548/attachment.sig\u003e"}