📅 Original date posted:2014-04-08
📝 Original message:On 04/08/2014 03:53 PM, Pieter Wuille wrote:
> Let me offer an alternative suggestion, which is compatible with the
> original default BIP32 structure:
> * You can use one seed across different chains, but the master nodes
> are separate.
> * To derive the master node from the seed, the key string "Bitcoin
> seed" is replaced by something chain-specific.
> * Every encoded node (including master nodes) has a chain-specific
> serialization magic.
This is possible, but I find it much more practical to use just one list
(assignment of coins to indexes) than to use two lists (assignment of
coins to key strings and to serialization magic).
Keeping two lists is harder and adds unnecessary friction. (Also I am
not very happy for the possibility we'll have to deal with key strings
"sCAMCo1N RULEZZZZ!!!! bRoUghT TO YoU bY M4rty" and serialization magic
that leads to prefix "lulz").
Also from wallet's implementer perspective it is a little easier to use
just one root node and then descend in tree as needed than to use method
you described.
--
Best Regards / S pozdravom,
Pavol Rusnak <stick at gk2.sk>
Pavol Rusnak [ARCHIVE] /
npub1wc…3hnuq
2023-06-07 15:17:51
in reply to nevent1q…rm3d
Author Public Key
npub1wccnjljxnarlx564vuc37hmuzuffurljevjnmuq4u0vjmh7e933sn3hnuqPublished at
2023-06-07 15:17:51Event JSON
{
"id": "7caadd47008636df20abdad7fc1b918c82a0ac35fe2ea9d0dcb7dd46f11cd450",
"pubkey": "7631397e469f47f3535567311f5f7c17129e0ff2cb253df015e3d92ddfd92c63",
"created_at": 1686151071,
"kind": 1,
"tags": [
[
"e",
"3d6a81230db6ab232d8356d3ea7e609f18aff1b8f11502ea70755e81b0de88f9",
"",
"root"
],
[
"e",
"d1d5567a146c3fc8e141516187f6254419818f2fb028bdeaba35ce58002f74fc",
"",
"reply"
],
[
"p",
"c632841665fccdabf021322b1d969539c9c1f829ceed38844fea24e8512962d7"
]
],
"content": "📅 Original date posted:2014-04-08\n📝 Original message:On 04/08/2014 03:53 PM, Pieter Wuille wrote:\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\nThis is possible, but I find it much more practical to use just one list\n(assignment of coins to indexes) than to use two lists (assignment of\ncoins to key strings and to serialization magic).\n\nKeeping two lists is harder and adds unnecessary friction. (Also I am\nnot very happy for the possibility we'll have to deal with key strings\n\"sCAMCo1N RULEZZZZ!!!! bRoUghT TO YoU bY M4rty\" and serialization magic\nthat leads to prefix \"lulz\").\n\nAlso from wallet's implementer perspective it is a little easier to use\njust one root node and then descend in tree as needed than to use method\nyou described.\n\n-- \nBest Regards / S pozdravom,\n\nPavol Rusnak \u003cstick at gk2.sk\u003e",
"sig": "7bc5f69f0bbf07016695d93f5d26c29ca0ca45ffbe94a6834e48b97f1bcbd42a253501d31131384275127b22cad521203b4bf6ff65cffa4539e309a099b1d5f0"
}