MIME-Version: 1.0
References: <68441995-c7d44f8b69d56a75112afa495bca5bf9@pmq6v.m5r2.onet>
In-Reply-To: <68441995-c7d44f8b69d56a75112afa495bca5bf9@pmq6v.m5r2.onet>
From: Lloyd Fournier <lloyd.fourn@gmail.com>
Date: Wed, 4 May 2022 10:26:46 +1000
Message-ID: <CAH5Bsr0rUuRrVoWO+xBGqwrTrJNwCp0akUD4OGB0RvU2ttWx6g@mail.gmail.com>
To: vjudeu@gazeta.pl, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000c88a2705de24af9e"
Subject: Re: [bitcoin-dev] Password-protected wallet on Taproot
Precedence: list

--000000000000c88a2705de24af9e
Content-Type: text/plain; charset="UTF-8"

Hi Vjudeu,

Perhaps this could make sense in some setting. e.g. instead of a hardware
device which protects your secret key via pin you use a pinless device but
you create a strong password and use a proper password hash to create
another key and put them in a 2-of-2. But make sure you don't use sha256 to
hash the password. Use a proper password hash. Keep in mind there's also
bip39 passwords which do a similar but this does involve entering them into
the possibly malicious hardware device.

Cheers,

LL

On Mon, 2 May 2022 at 03:56, vjudeu via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> It seems that Taproot allows us to protect each individual public key with
> a password. It could work in this way: we have some normal, Taproot-based
> public key, that is generated in a secure and random way, as it is today in
> Bitcoin Core wallet. Then, we can create another public key, just by taking
> password from the user, executing SHA-256 on that, and using it as a
> private key, so the second key will be just a brainwallet. Then, we can
> combine them in a Schnorr signature, forming 2-of-2 multisig, where the
> first key is totally random, and the second key is just a brainwallet that
> takes a password chosen by the user. By default, each key can be protected
> with the same password, used for the whole wallet, but it could be possible
> to choose different passwords for different addresses, if needed.
> Descriptors should handle that nicely, in the same way as they can be used
> to handle any other 2-of-2 multisig.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

<div dir=3D"ltr">Hi Vjudeu,<div><br></div><div>Perhaps this could make sens=
e in some setting. e.g. instead of a hardware device which protects your se=
cret key via pin you use a pinless device but you create a strong password =
and use a proper password hash to create another key and put them in a 2-of=
-2. But make sure you don&#39;t use sha256 to hash the password. Use a prop=
er password hash. Keep in mind there&#39;s also bip39 passwords which do a =
similar but this does involve entering them into the possibly malicious har=
dware device.</div><div><br></div><div>Cheers,</div><div><br></div><div>LL<=
/div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_a=
ttr">On Mon, 2 May 2022 at 03:56, vjudeu via bitcoin-dev &lt;<a href=3D"mai=
lto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundatio=
n.org</a>&gt; wrote:<br></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">It seems that Taproot allows us to protect each individual public key =
with a password. It could work in this way: we have some normal, Taproot-ba=
sed public key, that is generated in a secure and random way, as it is toda=
y in Bitcoin Core wallet. Then, we can create another public key, just by t=
aking password from the user, executing SHA-256 on that, and using it as a =
private key, so the second key will be just a brainwallet. Then, we can com=
bine them in a Schnorr signature, forming 2-of-2 multisig, where the first =
key is totally random, and the second key is just a brainwallet that takes =
a password chosen by the user. By default, each key can be protected with t=
he same password, used for the whole wallet, but it could be possible to ch=
oose different passwords for different addresses, if needed. Descriptors sh=
ould handle that nicely, in the same way as they can be used to handle any =
other 2-of-2 multisig.<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>

--000000000000c88a2705de24af9e--