From: Prayank <prayank@tutanota.de>
To: max@towardsliberty.com
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Wasabi Wallet 2.0 Testnet Release
Date: Wed, 2 Mar 2022 05:24:00 +0100 (CET) [thread overview]
Message-ID: <Mx7rhhv--3-2@tutanota.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1993 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 2913 bytes --]
next reply other threads:[~2022-03-02 4:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 4:24 Prayank [this message]
2022-03-10 12:33 ` [bitcoin-dev] Wasabi Wallet 2.0 Testnet Release nopara73
-- strict thread matches above, loose matches on Subject: below --
2022-03-01 20:48 Max Hillebrand
2022-03-01 22:50 ` nopara73
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Mx7rhhv--3-2@tutanota.de \
--to=prayank@tutanota.de \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=max@towardsliberty.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox