From: Damian Williamson <willtech@live.com.au>
To: Eric Voskuil <eric@voskuil.org>, Evan Klitzke <evan@eklitzke.org>,
"Bitcoin Protocol Discussion"
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] feature: Enhance privacy by change obfuscation
Date: Sun, 1 Apr 2018 14:37:13 +0000 [thread overview]
Message-ID: <PS2P216MB0179F3FE8D11A9161F0F502E9DA70@PS2P216MB0179.KORP216.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <BCD26605-01B0-437C-8D4A-68DA52055AFB@voskuil.org>
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
I note that Electrum v3.0.6 has an option to use multiple change addresses. It is off by default.
Regards,
Damian Williamson
________________________________
From: Eric Voskuil <eric@voskuil.org>
Sent: Monday, 19 March 2018 5:59:28 AM
To: Evan Klitzke; Bitcoin Protocol Discussion
Cc: Damian Williamson
Subject: Re: [bitcoin-dev] feature: Enhance privacy by change obfuscation
> This would be really expensive for the network due to the bloat in UTXO size, a cost everyone has to pay for.
Without commenting on the merits of this proposal, I’d just like to correct this common misperception. There is no necessary additional cost to the network from the count of unspent outputs. This perception arises from an implementation detail of particular node software. There is no requirement for redundant indexing of unspent outputs.
e
[-- Attachment #2: Type: text/html, Size: 1768 bytes --]
prev parent reply other threads:[~2018-04-01 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-18 1:34 [bitcoin-dev] feature: Enhance privacy by change obfuscation Damian Williamson
2018-03-18 5:50 ` Evan Klitzke
2018-03-18 7:07 ` Damian Williamson
2018-03-18 18:59 ` Eric Voskuil
2018-04-01 14:37 ` Damian Williamson [this message]
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=PS2P216MB0179F3FE8D11A9161F0F502E9DA70@PS2P216MB0179.KORP216.PROD.OUTLOOK.COM \
--to=willtech@live.com.au \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=eric@voskuil.org \
--cc=evan@eklitzke.org \
/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