📅 Original date posted:2015-04-09
📝 Original message:On Thu, Apr 9, 2015 at 1:16 PM, Kefkius <kefkius at maza.club> wrote:
> I've amended the proposal's "Motivation" section slightly for
> clarification. I'm not sure how a "cosigner_index" branch would benefit
> this proposal. Granted, I don't fully understand the benefits of the
> "cosigner_index" branch in BIP-0045. From what I understand, the
> "wallet" branch of my proposal seems to accomplish a similar goal.
Suppose Alice and Bob share a multi-sig wallet. Alice would like to
accept payment from Mallory, and Bob would like to accept payment from
Maude. So, they would each like to create a separate payment address.
If Alice and Bob both generate the same address, the incoming funds
would be mixed together (bad), and Mallory and Maude might learn about
the relationship between Alice and Bob (also bad).
Unfortunately, Alice and Bob are in a place where they can't
communicate (maybe Bob has no cell service). There is no way for Bob
to send a message like "I'm making a request on address_index N,
Alice, please use a different index for your request."
The cosigner_index solves this. When they set up the wallet, Alice and
Bob agree to always use a different value for the cosigner_index. That
way, addresses from Alice will never overlap with addresses from Bob,
since they are on different branches. Doing it this way adds privacy
and doesn't cost anything.
With this added in, your path would be:
m / purpose' / wallet' / coin_type / cosigner_index / change / address_index
XPUB's generated from your wallet would then be compatible with XPUB's
generated by other multi-sig wallets like CoPay, since the
(cosigner_index / change / address_index) structure stays the same.
-William Swanson
William Swanson [ARCHIVE] /
npub159…jtxgs
2023-06-07 15:32:21
in reply to nevent1q…zxk6
Author Public Key
npub159u2fkxuq00hvmtypwllna99xh0vk9k9jkk5w89taev70au0gwwsmjtxgsPublished at
2023-06-07 15:32:21Event JSON
{
"id": "b41d9bd2ca17cbadd5414eab947fa024b101c4d4bbcb2594fc3d10b644090e5c",
"pubkey": "a178a4d8dc03df766d640bbff9f4a535decb16c595ad471cabee59e7f78f439d",
"created_at": 1686151941,
"kind": 1,
"tags": [
[
"e",
"a3eafd4a0eb465d4acd06fbd4c0710e302efa659d70aadc00e533ecbab060a60",
"",
"root"
],
[
"e",
"da59ba27ffc4a815799ae6e29898d58c027fa2f137e3b4fc12d2378ee7e1e951",
"",
"reply"
],
[
"p",
"515d3994e186b3ad9a33cd2147d179924f66b958e63874d4ecad22fed0a5c23b"
]
],
"content": "📅 Original date posted:2015-04-09\n📝 Original message:On Thu, Apr 9, 2015 at 1:16 PM, Kefkius \u003ckefkius at maza.club\u003e wrote:\n\u003e I've amended the proposal's \"Motivation\" section slightly for\n\u003e clarification. I'm not sure how a \"cosigner_index\" branch would benefit\n\u003e this proposal. Granted, I don't fully understand the benefits of the\n\u003e \"cosigner_index\" branch in BIP-0045. From what I understand, the\n\u003e \"wallet\" branch of my proposal seems to accomplish a similar goal.\n\nSuppose Alice and Bob share a multi-sig wallet. Alice would like to\naccept payment from Mallory, and Bob would like to accept payment from\nMaude. So, they would each like to create a separate payment address.\nIf Alice and Bob both generate the same address, the incoming funds\nwould be mixed together (bad), and Mallory and Maude might learn about\nthe relationship between Alice and Bob (also bad).\n\nUnfortunately, Alice and Bob are in a place where they can't\ncommunicate (maybe Bob has no cell service). There is no way for Bob\nto send a message like \"I'm making a request on address_index N,\nAlice, please use a different index for your request.\"\n\nThe cosigner_index solves this. When they set up the wallet, Alice and\nBob agree to always use a different value for the cosigner_index. That\nway, addresses from Alice will never overlap with addresses from Bob,\nsince they are on different branches. Doing it this way adds privacy\nand doesn't cost anything.\n\nWith this added in, your path would be:\n\nm / purpose' / wallet' / coin_type / cosigner_index / change / address_index\n\nXPUB's generated from your wallet would then be compatible with XPUB's\ngenerated by other multi-sig wallets like CoPay, since the\n(cosigner_index / change / address_index) structure stays the same.\n\n-William Swanson",
"sig": "135d1022d5af712a1e914ff7f4801bf80684fd0919a885cef7a77b2c9c8f1f13c473f4d13e4a9f0f90eb73950161860ec908fb313900ad86b79c9ee84b93b674"
}