From: rhavar@protonmail•com
To: "Kenshiro \\[\\]" <tensiam@hotmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Payjoin privacy with the receiver of the transaction
Date: Thu, 21 Mar 2019 16:52:41 +0000 [thread overview]
Message-ID: <LUvvLGfixy2VQURUSkwxavfcxnQeLsUGvjm3o9iKW6EPOj0HIEeIlyhTUVIvaTcL_9NAY8k7CizkoKvSrQMq8b9fjDwxSzFvuAisboJ5jkQ=@protonmail.com> (raw)
In-Reply-To: <DB6PR10MB1832253A8D022C4A91573D49A6470@DB6PR10MB1832.EURPRD10.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 1792 bytes --]
I'm not really sure the problem you're describing, but it sounds like something that affects normal bitcoin transactions as well.
There's certainly some interesting about the idea of "pre-fragmenting" your wallet utxo so you can make (or in payjoin: receive) payments with better privacy aspects.However, it's pretty unlikely to be practical for normal users, as it'll generally result in pretty big and cost-ineffective transactions.
In general though, there's like a 1000 different things you can do with coin selection, utxo management (and payjoin contributed input selection) but more often than not you are just making just making 1 trade off for another and good solutions will be wildly different depending on how you use your wallet.
-Ryan
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, March 18, 2019 3:55 AM, Kenshiro \[\] via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> Hi,
>
> I think Payjoin can be a very good privacy solution for Bitcoin, but I have a question about it:
>
> - If a user has 1 BTC in a single address and make a payjoin payment to other person of 0.1 BTC using that address as input, the other person can see in a blockchain explorer the change address with an amount of 0.9 BTC. That's a serious privacy leak. I would like to know what will be the standard solution to this issue. An easy fix could be that the user wallet check if any address contains a BTC amount higher than a "safe" amount like 0.01 BTC or less. If some address exceed that amount the wallet could automatically make 1 payment to itself to split the amount in several addresses. In this way nobody receiving a payment from a user will ever know that he has a bitcoin balance higher than the "safe" amount.
>
> What do you think?
>
> Regards,
[-- Attachment #2: Type: text/html, Size: 2480 bytes --]
next prev parent reply other threads:[~2019-03-21 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 10:55 Kenshiro []
2019-03-21 16:52 ` rhavar [this message]
2019-03-22 10:23 ` Kenshiro []
2019-03-22 11:15 ` Kenshiro []
2019-03-22 16:05 ` ZmnSCPxj
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='LUvvLGfixy2VQURUSkwxavfcxnQeLsUGvjm3o9iKW6EPOj0HIEeIlyhTUVIvaTcL_9NAY8k7CizkoKvSrQMq8b9fjDwxSzFvuAisboJ5jkQ=@protonmail.com' \
--to=rhavar@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=tensiam@hotmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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