path: root/79/e51f118b81988e3e8effa948daa322f765e6c3

Return-Path: <hugo@nunchuk.io>
Received: from hemlock.osuosl.org (smtp2.osuosl.org [140.211.166.133])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 8BCF1C013A
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  9 Feb 2021 10:06:07 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by hemlock.osuosl.org (Postfix) with ESMTP id 7A4158624A
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  9 Feb 2021 10:06:07 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
Received: from hemlock.osuosl.org ([127.0.0.1])
 by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id of4tlyDNOHdk
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  9 Feb 2021 10:06:06 +0000 (UTC)
X-Greylist: delayed 00:20:06 by SQLgrey-1.7.6
Received: from mail-ua1-f54.google.com (mail-ua1-f54.google.com
 [209.85.222.54])
 by hemlock.osuosl.org (Postfix) with ESMTPS id 34B588545D
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  9 Feb 2021 10:06:06 +0000 (UTC)
Received: by mail-ua1-f54.google.com with SMTP id i3so5659099uai.3
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 09 Feb 2021 02:06:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=nunchuk-io.20150623.gappssmtp.com; s=20150623;
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to
 :cc; bh=fDXKRQJUEBuyGM8na51/IIcn/EBmM9ewtz/kvqFehRc=;
 b=k2RleMo0ztJ1LrXddLi4QV9IK+l13DvBEdbvSOo0nh3RvO/F6OhXeR4dAu240+CaiK
 drpLnMd0cPgudighlmtnS+OalPspgLec8cm+QKrSKCgU4Nk3ruBMoLzZcamygln13sqS
 uT2lbz9i+mEcuxKx7dUgoqPMtbJKSFH8J8wnqLkjIlrb5aji4P2ttnjz2IfClR0KTLhT
 xskHnnVke99nqKBBljFabzxLIVj/ZW1FowVIriC5yOCw0basOVpMphmFo1DyGOaKw8jR
 j3PZ/rKY6Xaa77BoPvzPUTIQfxHIHjSPxPBoxNiLuXePz3xH8w7xXJH8INQyuojkyNWG
 DYOA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=fDXKRQJUEBuyGM8na51/IIcn/EBmM9ewtz/kvqFehRc=;
 b=KMWpjFAPBFRoVc9hIZCaahOI185wsc6JNLmdhpLqr0V2/PvQ22QiZGu0zpTwbokaK9
 9LmIU9hjcOlNPOsbmuTpnwposecFspyd2OP1jIUMUxBRwm0QJn3jnS/6qANyqBuaqWXP
 BuAS3zUag1kYl3Nk2i8bg5T1Qt0FQM8rIJ3PNWxD6CdxEoPRXgNYjhmv36om1g9ZBcMr
 NjpuGjPB4Ez9O3BTCG9Tj0BCd7j/wqZOzC2M3yAQdKDZnL8/JCZZKXfhYUdHTaqbP3WJ
 tjCSrmR+S5h5fNUYO/1rIRzoMf8nsg2OvrBNwOYPL6m6Zp2RKsol+gr/i/UcQpgx/Z+h
 VARw==
X-Gm-Message-State: AOAM532/A3eHfVwYs/wdUHwkNTgjIGVdkfzfQKXKYfO33e1Z0ret+4wz
 O7/65xVr3g3+hiPBU8ualB/wdFvxjB0RiGi9BiZ2LFLPgJkIpOH8ZXk=
X-Google-Smtp-Source: ABdhPJxx1BI5kUNv6gJgaa8Kql/olLQBNKeaU15CMC8c0LpK5c3S2SzSkLNkuwt1N5wSd+JALOFOg0b41svLlU7s1yE=
X-Received: by 2002:ab0:7022:: with SMTP id u2mr4023757ual.63.1612865165072;
 Tue, 09 Feb 2021 02:06:05 -0800 (PST)
MIME-Version: 1.0
References: <CAPKmR9uyY70MhmVCh=C9DeyF2Tyxibux1E_bLPo00aW_h+OjLw@mail.gmail.com>
 <CACrqygA1JRA293joYOxxpSepiuFD=uVvQQy3wpuosYyLQHff-A@mail.gmail.com>
In-Reply-To: <CACrqygA1JRA293joYOxxpSepiuFD=uVvQQy3wpuosYyLQHff-A@mail.gmail.com>
From: Hugo Nguyen <hugo@nunchuk.io>
Date: Tue, 9 Feb 2021 02:05:54 -0800
Message-ID: <CAPKmR9tcR7gBfJ=EqJ60J=XvsreZgByL+HEfR0_YvwadJRWNhg@mail.gmail.com>
To: Christopher Allen <ChristopherA@lifewithalacrity.com>
Content-Type: multipart/alternative; boundary="0000000000003c308405bae46f6d"
X-Mailman-Approved-At: Tue, 09 Feb 2021 11:38:02 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Proposal: Bitcoin Secure Multisig Setup
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2021 10:06:07 -0000

--0000000000003c308405bae46f6d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Christopher,
Comments inline.

On Tue, Feb 9, 2021 at 1:31 AM Christopher Allen <
ChristopherA@lifewithalacrity.com> wrote:

> In the Airgapped Wallet Community we also have been investigating
> solutions, in particular as current common practice is is reuse the same
> xpub for all multisigs, for instance [90081696/48'/0'/0'/2']
> xpub6DYLEkDfCdHzh5FHGHDJksQvFqu6kYANa1sfo6fA8n5ZWkSwyCRVVzyq9LY2eNGB6T9BK=
DeGJp2ZarjRZHd7WB95nSaFEDhFMK6zSV6D49b
>
>
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.



> We=E2=80=99ve also have been looking into multi round commitment scheme, =
but
> wanted to align the UX so that it would work like to musig for users.
> Discussion on it is scattered, for instance
>
> https://github.com/BlockchainCommons/Airgapped-Wallet-Community/discussio=
ns/16#discussioncomment-212013
>
> Nothing got as far as your version though.
>
> So Concept ACK from Blockchain Commons. Less clear on your specifics
> though. We will review.
>
> Note that we are releasing a descriptor & multisig centric iOS and Androi=
d
> reference wallet soon so solving this correctly and having interoperabili=
ty
> with others is very important for our roadmap.
>

Thank you and good to know ! Look forward to solving this correctly as well=
.

Best,

Hugo


>
> =E2=80=94 Christopher Allen
>
>

--0000000000003c308405bae46f6d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Christopher,<br>Comments inline.</div><br><div cla=
ss=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Feb 9, 202=
1 at 1:31 AM Christopher Allen &lt;<a href=3D"mailto:ChristopherA@lifewitha=
lacrity.com">ChristopherA@lifewithalacrity.com</a>&gt; wrote:<br></div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto">In the Airg=
apped Wallet Community we also have been investigating solutions, in partic=
ular as current common practice is is reuse the same xpub for all multisigs=
, for instance [90081696/48&#39;/0&#39;/0&#39;/2&#39;] xpub6DYLEkDfCdHzh5FH=
GHDJksQvFqu6kYANa1sfo6fA8n5ZWkSwyCRVVzyq9LY2eNGB6T9BKDeGJp2ZarjRZHd7WB95nSa=
FEDhFMK6zSV6D49b</div><div dir=3D"auto"><br></div></blockquote><div><br>I d=
on&#39;t think reusing XPUBs inside different multisig wallets is a good id=
ea... For starters, loss of privacy in one wallet will immediately affect p=
rivacy of other wallets. I think multisig wallets should be completely fire=
walled from each other. That means one unique=C2=A0XPUB per wallet. This is=
 what we have been doing with the Nunchuk wallet.</div><div><br>=C2=A0</div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto"></div>=
<div dir=3D"auto">We=E2=80=99ve also have been looking into multi round com=
mitment scheme, but wanted to align the UX so that it would work like to mu=
sig for users. Discussion on it is scattered, for instance <div><a href=3D"=
https://github.com/BlockchainCommons/Airgapped-Wallet-Community/discussions=
/16#discussioncomment-212013" target=3D"_blank">https://github.com/Blockcha=
inCommons/Airgapped-Wallet-Community/discussions/16#discussioncomment-21201=
3</a></div><div dir=3D"auto"><br></div>Nothing got as far as your version t=
hough.</div><div dir=3D"auto"><br></div><div dir=3D"auto">So Concept ACK fr=
om Blockchain Commons. Less clear on your specifics though. We will review.=
</div><div dir=3D"auto"><br></div><div dir=3D"auto">Note that we are releas=
ing a descriptor &amp; multisig centric iOS and Android reference wallet so=
on so solving this correctly and having interoperability with others is ver=
y important for our roadmap.</div></blockquote><div><br>Thank you and good =
to know ! Look forward to solving this correctly as well.<br><br>Best,<br><=
br>Hugo</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><div dir=3D"auto"><br></div><div dir=3D"auto">=E2=80=94 Christopher Al=
len</div><div dir=3D"auto"><br></div>
</blockquote></div></div>

--0000000000003c308405bae46f6d--