1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
|
Return-Path: <vjudeu@gazeta.pl>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137])
by lists.linuxfoundation.org (Postfix) with ESMTP id C0616C002D
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 1 May 2022 16:28:52 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp4.osuosl.org (Postfix) with ESMTP id 9E0E9408A1
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 1 May 2022 16:28:52 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level:
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5
tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: smtp4.osuosl.org (amavisd-new);
dkim=pass (1024-bit key) header.d=gazeta.pl
Received: from smtp4.osuosl.org ([127.0.0.1])
by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id G_95Ado5ftZD
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 1 May 2022 16:28:51 +0000 (UTC)
X-Greylist: delayed 00:10:03 by SQLgrey-1.8.0
Received: from smtpo79.poczta.onet.pl (smtpo79.poczta.onet.pl [141.105.16.29])
by smtp4.osuosl.org (Postfix) with ESMTPS id 8F12740872
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 1 May 2022 16:28:51 +0000 (UTC)
Received: from pmq6v.m5r2.onet (pmq6v.m5r2.onet [10.174.33.77])
by smtp.poczta.onet.pl (Onet) with ESMTP id 4Krrxr3xlSz1BrQ
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 1 May 2022 18:18:40 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gazeta.pl; s=2013;
t=1651421920; bh=B6AnFPyJYZsGF9ZRt/nr1hb02K2tzIJo9j7fL/JPUnw=;
h=From:To:Date:Subject:From;
b=aD9Meu78lalvW+v15MEHiiRBhPpQNAPG78aOgGfZDFKaxsFCCKOhnCbojbqzNW79D
ZtdBYg1mq1ZgSgztxl13u+/dDfY1yrYqm+Soum7Q8yk4jbFhRD4hTLwuhtu3b4FLI9
dIZ5x5/ZUzjzFmfYzdMIEk2O//20Vy1f/V3IZPOg=
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Received: from [5.173.233.13] by pmq6v.m5r2.onet via HTTP id ;
Sun, 01 May 2022 18:18:40 +0200
From: vjudeu@gazeta.pl
X-Priority: 3
To: bitcoin-dev@lists.linuxfoundation.org
Date: Sun, 01 May 2022 18:18:40 +0200
Message-Id: <68441995-c7d44f8b69d56a75112afa495bca5bf9@pmq6v.m5r2.onet>
X-Mailer: onet.poczta
X-Onet-PMQ: <vjudeu@gazeta.pl>;5.173.233.13;PL;1
X-Mailman-Approved-At: Sun, 01 May 2022 17:56:09 +0000
Subject: [bitcoin-dev] Password-protected wallet on Taproot
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: Sun, 01 May 2022 16:28:52 -0000
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 p=
ublic 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 priva=
te 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 i=
s totally random, and the second key is just a brainwallet that takes a pas=
sword chosen by the user. By default, each key can be protected with the sa=
me 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.
|
