{"type":"rich","version":"1.0","author_name":"npub1xvnnyhz8e4eklaakjc9xgm5w8pzkuckt923uacz2cftqdqx23g7q3c5rqg","author_url":"https://nostr.ae/npub1xvnnyhz8e4eklaakjc9xgm5w8pzkuckt923uacz2cftqdqx23g7q3c5rqg","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-03-27\n📝 Original message:The benefit I see is avoiding reuse of keys between coins while not having\neach wallet implementation have to know about each coin in order to scan\nfor transactions.  Wallet X supports Doge and Bitcoin.  If both used a\nshared sequence of keys, say the first two end up Bitcoin, then 10 Doge,\nthen some more Bitcoin.  If you took this seed to Wallet Y, which only\nsupports Bitcoin (either the wallet's support or what is installed on the\nsystem it's being used), it will see a gap of 10 addresses, and presume no\nmore scanning with a 5 gap limit.  The alternative is to reuse keys for\neach coin.\n\nIt also seems like a solution might be to only expect interoperability on a\nsingle sequence, and provide backups of each final sequence to use between\ndifferent wallet implementations.  This allows flexibility in hierarchies\ndepending on needs and support of wallet, but allows sharing.  The short\nseed would only be useful for the same wallet, but sharing between wallets\nwould use the longer keys.  That will give predictable behavior for users\n(although less friendly) and lead to less errors.\n\n-Allen\n\n\nOn Thu, Mar 27, 2014 at 11:28 AM, Pieter Wuille \u003cpieter.wuille at gmail.com\u003ewrote:\n\n\u003e On Thu, Mar 27, 2014 at 5:21 PM, Pavol Rusnak \u003cstick at gk2.sk\u003e wrote:\n\u003e \u003e Cointype in path is for separation purposes, not for identification.\n\u003e\n\u003e I don't understand what that gains you.\n\u003e\n\u003e --\n\u003e Pieter\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\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-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140327/0e05360a/attachment.html\u003e"}