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
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
|
Return-Path: <prayank@tutanota.de>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138])
by lists.linuxfoundation.org (Postfix) with ESMTP id 22332C000B
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 2 Mar 2022 04:24:05 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp1.osuosl.org (Postfix) with ESMTP id 0A45081AF6
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 2 Mar 2022 04:24:05 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.099
X-Spam-Level:
X-Spam-Status: No, score=-1.099 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, BITCOIN_IMGUR=1, DKIM_SIGNED=0.1,
DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1,
HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001,
SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: smtp1.osuosl.org (amavisd-new);
dkim=pass (2048-bit key) header.d=tutanota.de
Received: from smtp1.osuosl.org ([127.0.0.1])
by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id j5AtXMdPCQ7a
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 2 Mar 2022 04:24:04 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
Received: from w1.tutanota.de (w1.tutanota.de [81.3.6.162])
by smtp1.osuosl.org (Postfix) with ESMTPS id D2BA4818EC
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 2 Mar 2022 04:24:03 +0000 (UTC)
Received: from w3.tutanota.de (unknown [192.168.1.164])
by w1.tutanota.de (Postfix) with ESMTP id 0D422FA00DD;
Wed, 2 Mar 2022 04:24:01 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1646195040;
s=s1; d=tutanota.de;
h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Cc:Cc:Date:Date:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:Sender;
bh=UNqEvQzooLNg+NUY7HxqrmZy1H+P/Re4QI3Pis5i28s=;
b=ueP/qCEBigqi+E6vBUm+LgNgbrNFa/LZW+w+XwJyzzqEZXcgAKo1d33nxZWlJrum
XTA3YNebq1uw5DtaJz+Ej6eL3Im1sKCosngYBVuPO/bLTgKbSAaDNICevnEw4eKm4f7
+fxyNNawIOi7rGHc+pDyaUUjsj7/K82YOI5N/4LC3/bXp5lZye7mBKCLO6J++qfSrx7
WUEz2vh9m9HlO1ks6dNk+ZXb0/6VTxx4x/HLpbuDOJ49XP/elZUE1osgqnER0Mynhgr
fNuPBgh2tLvJNlA6ZxVAa4EwrKvxETpkZd/OKuYN/x9CMK8tx1qqzaQhoTPXQ0gqfqj
9NXoDS4aOQ==
Date: Wed, 2 Mar 2022 05:24:00 +0100 (CET)
From: Prayank <prayank@tutanota.de>
To: max@towardsliberty.com
Message-ID: <Mx7rhhv--3-2@tutanota.de>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_70503_1930018177.1646195041038"
X-Mailman-Approved-At: Wed, 09 Mar 2022 21:27:35 +0000
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Wasabi Wallet 2.0 Testnet Release
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: Wed, 02 Mar 2022 04:24:05 -0000
------=_Part_70503_1930018177.1646195041038
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Hi Max,
> Whenever the user wants to spend bitcoin to an address, the wallet automatically selects those private coins with sufficient sats, coin control is displayed to the user.
1.There are no 'private' coins. Every coin is public in Bitcoin.
2.Since, the wallet assumes some coins as 'private' based on certain things it can be misleading for the user. Privacy depends on the things users want to share with others.
3.There is no coin control in Wasabi Wallet 2.
> However, when the private balance is insufficient to make the payment, the user has the option to adjust the coin selection with the help of the previously provided contact labels.
User does not select coins because they are never shared with the user in the first place.
[Selecting some labels][1] with misleading text 'who can see this transaction' does not look helpful.
> Wasabi also suggests the user to slightly adjust the payment amount so as to avoid the creation of a change utxo, decreasing fees and improving future privacy.
Privacy involved in using a change or not using it is debatable. Not using a change address makes it easier to understand who might be the recipient in a transaction whereas using a change address same as other outputs would be difficult to analyze for possible recipients.
Wasabi wallet does not have different types of addresses to use for a change however [Bitcoin Core][2] recently made some related improvement which would improve privacy.
> We kindly ask for your help testing the completely new UI/UX
As WW2 is not developed for power users (mentioned by developers working on Wasabi), I am not sure if bitcoin dev mailing list would be the best place to look for newbies. As far as issues are concerned, there are several things not fixed and shared in different GitHub issues or discussions. These include privacy, security and other things.
[1]: https://i.imgur.com/Gxjmhau.png
[2]: https://github.com/bitcoin/bitcoin/pull/23789
--
Prayank
A3B1 E430 2298 178F
------=_Part_70503_1930018177.1646195041038
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF-8=
">
</head>
<body>
<div>Hi Max,<br></div><div dir=3D"auto"><br></div><div dir=3D"auto">> Wh=
enever the user wants to spend bitcoin to an address, the wallet automatica=
lly selects those private coins with sufficient sats, coin control is displ=
ayed to the user.<br></div><div dir=3D"auto"><br></div><div dir=3D"auto">1.=
There are no 'private' coins. Every coin is public in Bitcoin.<br></div><di=
v dir=3D"auto"><br></div><div dir=3D"auto">2.Since, the wallet assumes some=
coins as 'private' based on certain things it can be misleading for the us=
er. Privacy depends on the things users want to share with others.<br></div=
><div dir=3D"auto"><br></div><div dir=3D"auto">3.There is no coin control i=
n Wasabi Wallet 2. <br></div><div dir=3D"auto"><br></div><div dir=3D"auto">=
> However, when the private balance is insufficient to make the payment,=
the user has the option to adjust the coin selection with the help of the =
previously provided contact labels.<br></div><div dir=3D"auto"><br></div><d=
iv dir=3D"auto">User does not select coins because they are never shared wi=
th the user in the first place.<br></div><div dir=3D"auto"><br></div><div d=
ir=3D"auto">[Selecting some labels][1] with misleading text 'who can see th=
is transaction' does not look helpful.<br></div><div><div><br></div><div>&g=
t; Wasabi also suggests the user to slightly adjust the payment amount so a=
s to avoid the creation of a change utxo, decreasing fees and improving fut=
ure privacy.<br></div><div dir=3D"auto"><br></div><div dir=3D"auto">Privacy=
involved in using a change or not using it is debatable. Not using a chang=
e address makes it easier to understand who might be the recipient in a tra=
nsaction whereas using a change address same as other outputs would be diff=
icult to analyze for possible recipients.<br></div><div dir=3D"auto"><br></=
div><div dir=3D"auto">Wasabi wallet does not have different types of addres=
ses to use for a change however [Bitcoin Core][2] recently made some relate=
d improvement which would improve privacy.<br></div><div dir=3D"auto"><br><=
/div><div dir=3D"auto">> We kindly ask for your help testing the complet=
ely new UI/UX<br></div><div dir=3D"auto"><br></div><div dir=3D"auto">As WW2=
is not developed for power users (mentioned by developers working on Wasab=
i), I am not sure if bitcoin dev mailing list would be the best place to lo=
ok for newbies. As far as issues are concerned, there are several things no=
t fixed and shared in different GitHub issues or discussions. These include=
privacy, security and other things.<br></div><div dir=3D"auto"><br></div><=
div dir=3D"auto"><div><br></div><div>[1]: https://i.imgur.com/Gxjmhau.png<b=
r></div><div dir=3D"auto">[2]: https://github.com/bitcoin/bitcoin/pull/2378=
9<br></div></div><div><br><br>-- <br></div></div><div>Prayank<br></div><div=
><br></div><div dir=3D"auto">A3B1 E430 2298 178F<br></div> </body>
</html>
------=_Part_70503_1930018177.1646195041038--
|
