From: Damian Williamson <willtech@live•com.au>
To: Evan Klitzke <evan@eklitzke•org>,
"bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] feature: Enhance privacy by change obfuscation
Date: Sun, 18 Mar 2018 07:07:58 +0000 [thread overview]
Message-ID: <PS2P216MB017905271ED76F964F4615829DD50@PS2P216MB0179.KORP216.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <874lleexud.fsf@eklitzke.org>
[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]
Alright, but even if two (or more) of the change outputs were linked in a future transaction, no-one can tell if they are still linked to your wallet or not unless there is also an additional re-used address on the new transaction input side that has also been previously linked to one of the inputs on the transaction creating the change.
Yes, I understand the additional cost but still thought it worthy of consideration.
Regards,
Damian Williamson
________________________________
From: Evan Klitzke <evan@eklitzke•org>
Sent: Sunday, 18 March 2018 4:50:34 PM
To: Damian Williamson; Bitcoin Protocol Discussion
Subject: Re: [bitcoin-dev] feature: Enhance privacy by change obfuscation
Damian Williamson via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> writes:
> Operation: Provide a user selectable 'Enhanced privacy' option for
> transaction creation, when true the transaction randomly distributes
> change across up to twenty output addresses (minimum five?), provided
> each output is not dust.
This would be really expensive for the network due to the bloat in UTXO
size, a cost everyone has to pay for. Not to mention the fact that it
doesn't really seem that private, as the wallet is likely going to have
to rejoin those inputs in future transactions (and the user will have to
pay a high transaction fee as a result).
--
Evan Klitzke
https://eklitzke.org/
[-- Attachment #2: Type: text/html, Size: 2511 bytes --]
next prev parent reply other threads:[~2018-03-18 7:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-18 1:34 Damian Williamson
2018-03-18 5:50 ` Evan Klitzke
2018-03-18 7:07 ` Damian Williamson [this message]
2018-03-18 18:59 ` Eric Voskuil
2018-04-01 14:37 ` Damian Williamson
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=PS2P216MB017905271ED76F964F4615829DD50@PS2P216MB0179.KORP216.PROD.OUTLOOK.COM \
--to=willtech@live$(echo .)com.au \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=evan@eklitzke$(echo .)org \
/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