📅 Original date posted:2021-02-09
📝 Original message:On Tue, Feb 9, 2021 at 2:19 AM Christopher Allen <
ChristopherA at lifewithalacrity.com> wrote:
>
>
> On Tue, Feb 9, 2021 at 2:06 AM Hugo Nguyen <hugo at nunchuk.io> wrote:
>
>>
>> I don't think reusing XPUBs inside different multisig wallets is a good
>> idea... For starters, loss of privacy in one wallet will immediately affect
>> privacy of other wallets. I think multisig wallets should be completely
>> firewalled from each other. That means one unique XPUB per wallet. This is
>> what we have been doing with the Nunchuk wallet.
>>
>
> To be clear, I have stated repeatedly that xpub reuse into multisig is a
> poor practice. However, finding a trustless solution when a wallet is
> airgapped with no network, or is stateless like Trezor, is quite hard.
>
> The challenge also includes how does an airgapped or stateless wallet know
> that it is talking to the same process on the other side that that it gave
> the xpub to in the first place. Without state to allow for a commitment, or
> at least a TOFU, a cosigner who thought he was part of a 3 of 5 could
> discover that he instead is in a 2 of 3, or in a script with an OR, as some
> form of scam.
>
The shared secret approach that I mentioned in the proposal actually can
help you here. The TOKEN doubles as a session ID - thereby establishing a
common state on both sides.
Best,
Hugo
>
> — Christopher Allen
>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210209/51b3281e/attachment.html>;
Hugo Nguyen [ARCHIVE] /
npub1jq…5jqeg
2023-06-07 18:28:33
in reply to nevent1q…ls63
Author Public Key
npub1jqxs4ftunmm8qjyw9s80hpcayewkjfhpxund29l9qvzy7xqx4duq85jqegPublished at
2023-06-07 18:28:33Event JSON
{
"id": "39183ca287e293c2b5eeb360d99db59d446e1b6b787bc12608e72ff19a1cf50a",
"pubkey": "900d0aa57c9ef670488e2c0efb871d265d6926e13726d517e503044f1806ab78",
"created_at": 1686162513,
"kind": 1,
"tags": [
[
"e",
"86ad6c37ed92954d8359f9dbcd43bb8becf51e4b072d4e707f08909fe0306de5",
"",
"root"
],
[
"e",
"8a1fd7b5524cd1b52b41e6ece62fe152097bd82f2792a796fc2c02538d2bafd4",
"",
"reply"
],
[
"p",
"900d0aa57c9ef670488e2c0efb871d265d6926e13726d517e503044f1806ab78"
]
],
"content": "📅 Original date posted:2021-02-09\n📝 Original message:On Tue, Feb 9, 2021 at 2:19 AM Christopher Allen \u003c\nChristopherA at lifewithalacrity.com\u003e wrote:\n\n\u003e\n\u003e\n\u003e On Tue, Feb 9, 2021 at 2:06 AM Hugo Nguyen \u003chugo at nunchuk.io\u003e wrote:\n\u003e\n\u003e\u003e\n\u003e\u003e I don't think reusing XPUBs inside different multisig wallets is a good\n\u003e\u003e idea... For starters, loss of privacy in one wallet will immediately affect\n\u003e\u003e privacy of other wallets. I think multisig wallets should be completely\n\u003e\u003e firewalled from each other. That means one unique XPUB per wallet. This is\n\u003e\u003e what we have been doing with the Nunchuk wallet.\n\u003e\u003e\n\u003e\n\u003e To be clear, I have stated repeatedly that xpub reuse into multisig is a\n\u003e poor practice. However, finding a trustless solution when a wallet is\n\u003e airgapped with no network, or is stateless like Trezor, is quite hard.\n\u003e\n\u003e The challenge also includes how does an airgapped or stateless wallet know\n\u003e that it is talking to the same process on the other side that that it gave\n\u003e the xpub to in the first place. Without state to allow for a commitment, or\n\u003e at least a TOFU, a cosigner who thought he was part of a 3 of 5 could\n\u003e discover that he instead is in a 2 of 3, or in a script with an OR, as some\n\u003e form of scam.\n\u003e\n\nThe shared secret approach that I mentioned in the proposal actually can\nhelp you here. The TOKEN doubles as a session ID - thereby establishing a\ncommon state on both sides.\n\nBest,\nHugo\n\n\n\u003e\n\u003e — Christopher Allen\n\u003e\n\u003e\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210209/51b3281e/attachment.html\u003e",
"sig": "ce607d36662f7c8adcbd4d9434eeb4c3f89503beb0f3acd7458185246a9108f25bc02b5d685f5e8d05bd32e49bb431503e6ae18a1db62bd2bcf7a5100a6c2fa3"
}