{"type":"rich","version":"1.0","author_name":"npub1tjephawh7fdf6358jufuh5eyxwauzrjqa7qn50pglee4tayc2ntqcjtl6r","author_url":"https://nostr.ae/npub1tjephawh7fdf6358jufuh5eyxwauzrjqa7qn50pglee4tayc2ntqcjtl6r","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-04-08\n📝 Original message:I see the cause of our disagreement now.\n\nYou actually want to share a single BIP32 tree across different\ncurrency types, but do it in a way that guarantees that they never use\nthe same keys.\n\nI would have expected that different chains would use independent\nchains, and have serializations encode which chain they belong to.\n\nLet me offer an alternative suggestion, which is compatible with the\noriginal default BIP32 structure:\n* You can use one seed across different chains, but the master nodes\nare separate.\n* To derive the master node from the seed, the key string \"Bitcoin\nseed\" is replaced by something chain-specific.\n* Every encoded node (including master nodes) has a chain-specific\nserialization magic.\n\nThis is in practice almost the same as your suggestion, except that\nthe m/cointype' in m/cointype'/account'/change/n is replaced by\ndifferent masters. The only disadvantage I see is that you do not have\na way to encode the \"super master\" that is the parent of all\nchain-specific masters. You can - and with the same security\nproperties - encode the seed, though.\n\n-- \nPieter\n\n\nOn Tue, Apr 8, 2014 at 3:43 PM, slush \u003cslush at centrum.cz\u003e wrote:\n\u003e tl;dr;\n\u003e\n\u003e It is dangerous to expect that other seed than \"xprv\" does not contain\n\u003e bitcoins or that \"xprv\" contains only bitcoins, because technically are both\n\u003e situations possible. It is still safer to do the lookup; the magic itself is\n\u003e ambiguous.\n\u003e\n\u003e Marek\n\u003e\n\u003e On Tue, Apr 8, 2014 at 3:40 PM, slush \u003cslush at centrum.cz\u003e wrote:\n\u003e\u003e\n\u003e\u003e\n\u003e\u003e Serialization magic of bip32 seed is in my opinion completely unnecessary.\n\u003e\u003e Most of software does not care about it anyway; You can use xprv/xpub pair\n\u003e\u003e for main net, testnet, litecoin, dogecoin, whatevercoin.\n\u003e\u003e\n\u003e\u003e Instead using the same seed (xprv) and then separate the chains *inside*\n\u003e\u003e the bip32 path seems more useful to me.\n\u003e\u003e\n\u003e\u003e Marek\n\u003e\n\u003e"}