📅 Original date posted:2014-03-27
📝 Original message:The idea was to use the magic number as the source for cointype. If it's
too big, as Tamas showed, perhaps a hash of it, and for coins without a
magic number, a hash of their name (or some unique identifier).
That being said, I agree with Andreas that something that is 90%
inter-operable seems very dangerous and will give people false expectations
when they miss the corner cases. If the structure isn't going to be shared
completely and have all support shared, having it completely incompatible
along with a mechanism for converting part of it to another wallet seems
superior. The worst types of losses will occur when someone tests out
something with a limited use case, sees that it appears to work, makes
dangerous assumptions, then gets burned when it's too late.
-Allen
On Thu, Mar 27, 2014 at 11:06 AM, Pavol Rusnak <stick at gk2.sk> wrote:
> On 03/27/2014 04:57 PM, Allen Piscitello wrote:
> > Don't most of these coins have a magic number already assigned that is
> > unique? (0xD9B4BEF9 for Bitcoin, 0x0709110B for Testnet, FBC0XB6DB for
> > Litecoin, etc...). This seems like a good candidate for identifying
> coins,
> > and also supports Testnet cases well. Maybe there are some alts without
> > such a magic number that might prevent that?
>
> That magic number is something I find very unfortunate and superflous in
> BIP-32 design. Its only purpose is to distinguish BIP-32 trees for
> various altcoins, but it doesn't make sense at all once you start
> storing various altcoins in the same tree using the proposed
> /m/cointype/reserved'/account'/change/n scheme.
>
> I would love to see that removed from BIP-32 and use always
> 0x0488B21E/0x0488ADE4 (xpub/xpriv), but that is for different discussion
> I guess.
>
> --
> Best Regards / S pozdravom,
>
> Pavol Rusnak <stick at gk2.sk>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140327/e7aa5555/attachment.html>;
Allen Piscitello [ARCHIVE] /
npub1xv…c5rqg
2023-06-07 15:16:18
in reply to nevent1q…jvz7
Author Public Key
npub1xvnnyhz8e4eklaakjc9xgm5w8pzkuckt923uacz2cftqdqx23g7q3c5rqgPublished at
2023-06-07 15:16:18Event JSON
{
"id": "f63db2b4b9d80f803405580a0b61e7dd3b37fa349b71bfc6805d4572c05fa051",
"pubkey": "3327325c47cd736ff7b6960a646e8e38456e62cb2aa3cee04ac2560680ca8a3c",
"created_at": 1686150978,
"kind": 1,
"tags": [
[
"e",
"d9ddea79394f356d989e65ab112610cc90e9929cf3c160da3cfe266aeba22200",
"",
"root"
],
[
"e",
"e3b2019cb04ec23f7015d1058566d82bd818279bc6ed9db05b533a20559d1b83",
"",
"reply"
],
[
"p",
"7631397e469f47f3535567311f5f7c17129e0ff2cb253df015e3d92ddfd92c63"
]
],
"content": "📅 Original date posted:2014-03-27\n📝 Original message:The idea was to use the magic number as the source for cointype. If it's\ntoo big, as Tamas showed, perhaps a hash of it, and for coins without a\nmagic number, a hash of their name (or some unique identifier).\n\nThat being said, I agree with Andreas that something that is 90%\ninter-operable seems very dangerous and will give people false expectations\nwhen they miss the corner cases. If the structure isn't going to be shared\ncompletely and have all support shared, having it completely incompatible\nalong with a mechanism for converting part of it to another wallet seems\nsuperior. The worst types of losses will occur when someone tests out\nsomething with a limited use case, sees that it appears to work, makes\ndangerous assumptions, then gets burned when it's too late.\n\n-Allen\n\n\nOn Thu, Mar 27, 2014 at 11:06 AM, Pavol Rusnak \u003cstick at gk2.sk\u003e wrote:\n\n\u003e On 03/27/2014 04:57 PM, Allen Piscitello wrote:\n\u003e \u003e Don't most of these coins have a magic number already assigned that is\n\u003e \u003e unique? (0xD9B4BEF9 for Bitcoin, 0x0709110B for Testnet, FBC0XB6DB for\n\u003e \u003e Litecoin, etc...). This seems like a good candidate for identifying\n\u003e coins,\n\u003e \u003e and also supports Testnet cases well. Maybe there are some alts without\n\u003e \u003e such a magic number that might prevent that?\n\u003e\n\u003e That magic number is something I find very unfortunate and superflous in\n\u003e BIP-32 design. Its only purpose is to distinguish BIP-32 trees for\n\u003e various altcoins, but it doesn't make sense at all once you start\n\u003e storing various altcoins in the same tree using the proposed\n\u003e /m/cointype/reserved'/account'/change/n scheme.\n\u003e\n\u003e I would love to see that removed from BIP-32 and use always\n\u003e 0x0488B21E/0x0488ADE4 (xpub/xpriv), but that is for different discussion\n\u003e I guess.\n\u003e\n\u003e --\n\u003e Best Regards / S pozdravom,\n\u003e\n\u003e Pavol Rusnak \u003cstick at gk2.sk\u003e\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/e7aa5555/attachment.html\u003e",
"sig": "8c2d001c57d110f29f1fb66f8f2a8c3a77cb22b84b5746da692cd11126262a45324ba54a937c294933ed58b3a0f1797d92c9c9e8a0b6a309fd60dce42b00278f"
}