📅 Original date posted:2014-09-23
📝 Original message:This topic has been touched on briefly here before, but I wanted to
solidify it and propose it as a BIP if there is wider support for it.
Also, the topic is difficult to discuss without lots of pictures -- so
that's what I've done (mainly to describe it to my team, but also as
general documentation). It's in presentation form:
https://s3.amazonaws.com/bitcoinarmory-media/MultisigWalletNoCollide.pdf
The proposal is that for an M-of-N multisig wallet based on BIP32, there
should be N internal chains and N external chains. Each party is
assigned a chain based on the lexicographic ordering of their wallet's
root public key in the multisig. This guarantees that no parties are
generating and distributing the same addresses, and also provides a
certain level of built-in book-keeping. Coins being received on chain
2*x were created by participant x (receiving), and coins received on
2*x+1 are change outputs created by participant x (outgoing). Thus,
it's easy from simply looking at the wallet structure who was
responsible for which transactions.
Alternatively, we could change it to suggest that each "device" is
assigned a pair of chains. For a 2-of-3 there may 3 participants plus a
CFO with a "watch-only" version of the multisig wallet. Then you might
use four pairs of chains. I'm just not sure how they would be assigned.
If this has been proposed before, then consider this my contribution to
documentation.
-Alan
P.S. -- "No-Collision Mode" is not a great name. Happy to take
suggestions for changing it.
Alan Reiner [ARCHIVE] /
npub1sm…mnq7h
2023-06-07 15:25:52
in reply to nevent1q…x93g
Author Public Key
npub1sm6zhjmk5scuz294jmpkw99wwwjzetjgwp4fu4gn6utqgdz87hkqamnq7hPublished at
2023-06-07 15:25:52Event JSON
{
"id": "e3b8f55cd00e59cca2b0757d164e54825e84c5995500d5a60464618319880247",
"pubkey": "86f42bcb76a431c128b596c36714ae73a42cae48706a9e5513d716043447f5ec",
"created_at": 1686151552,
"kind": 1,
"tags": [
[
"e",
"38c45bfae86c0f7b064209d993d33308368e19f80a41e12e5781fe978197c79c",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2014-09-23\n📝 Original message:This topic has been touched on briefly here before, but I wanted to\nsolidify it and propose it as a BIP if there is wider support for it. \nAlso, the topic is difficult to discuss without lots of pictures -- so\nthat's what I've done (mainly to describe it to my team, but also as\ngeneral documentation). It's in presentation form:\n\nhttps://s3.amazonaws.com/bitcoinarmory-media/MultisigWalletNoCollide.pdf\n\nThe proposal is that for an M-of-N multisig wallet based on BIP32, there\nshould be N internal chains and N external chains. Each party is\nassigned a chain based on the lexicographic ordering of their wallet's\nroot public key in the multisig. This guarantees that no parties are\ngenerating and distributing the same addresses, and also provides a\ncertain level of built-in book-keeping. Coins being received on chain\n2*x were created by participant x (receiving), and coins received on\n2*x+1 are change outputs created by participant x (outgoing). Thus,\nit's easy from simply looking at the wallet structure who was\nresponsible for which transactions.\n\nAlternatively, we could change it to suggest that each \"device\" is\nassigned a pair of chains. For a 2-of-3 there may 3 participants plus a\nCFO with a \"watch-only\" version of the multisig wallet. Then you might\nuse four pairs of chains. I'm just not sure how they would be assigned.\n\nIf this has been proposed before, then consider this my contribution to\ndocumentation. \n-Alan\n\nP.S. -- \"No-Collision Mode\" is not a great name. Happy to take\nsuggestions for changing it.",
"sig": "8865d5c43772cf0b79c1b7c477f39ba9a976e2c28171923425d9d227c16a1566ec569f3a46d0815c28bf42dbf7e9dc97f89caa82b1821a87b75201c8df655b5f"
}