📅 Original date posted:2014-04-08
📝 Original message:+1
I would prefer that solution...
Le 08/04/2014 15:53, Pieter Wuille a écrit :
> I see the cause of our disagreement now.
>
> You actually want to share a single BIP32 tree across different
> currency types, but do it in a way that guarantees that they never use
> the same keys.
>
> I would have expected that different chains would use independent
> chains, and have serializations encode which chain they belong to.
>
> 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 in practice almost the same as your suggestion, except that
> the m/cointype' in m/cointype'/account'/change/n is replaced by
> different masters. The only disadvantage I see is that you do not have
> a way to encode the "super master" that is the parent of all
> chain-specific masters. You can - and with the same security
> properties - encode the seed, though.
>
Thomas Voegtlin [ARCHIVE] /
npub10f…7ej47
2023-06-07 15:17:51
in reply to nevent1q…cu4j
Author Public Key
npub10f96gqrsu4qpygfgvuvzce47aavjvql703egfde0l2hua8dzpszs67ej47Published at
2023-06-07 15:17:51Event JSON
{
"id": "42acbce74481e95e3840181288b39d49506733e5e13b38961a8639964b212f2a",
"pubkey": "7a4ba40070e54012212867182c66beef592603fe7c7284b72ffaafce9da20c05",
"created_at": 1686151071,
"kind": 1,
"tags": [
[
"e",
"3d6a81230db6ab232d8356d3ea7e609f18aff1b8f11502ea70755e81b0de88f9",
"",
"root"
],
[
"e",
"b7c952f9bf67fe5aa3411a635d174bbc097dd3d0673adb67ed4da88c5ff3ff3c",
"",
"reply"
],
[
"p",
"5cb21bf5d7f25a9d46879713cbd32433bbc10e40ef813a3c28fe7355f49854d6"
]
],
"content": "📅 Original date posted:2014-04-08\n📝 Original message:+1\n\nI would prefer that solution...\n\n\n\nLe 08/04/2014 15:53, Pieter Wuille a écrit :\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",
"sig": "07aff3da9d72ec3134ebca26a99ed1864a13f2ca127bebfb0d0b25a3c0a0cc7247e4a86fca4ff60e2e74283f9f0bcd574577920328535bfd3e53befb2afa0a55"
}