📅 Original date posted:2018-03-18
📝 Original message: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 at 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 at 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/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180318/adae0170/attachment.html>;
Damian Williamson [ARCHIVE] /
npub1sp…8lz2h
2023-06-07 18:11:17
in reply to nevent1q…72ts
Author Public Key
npub1spe4rkz350zpn7h2pz07t8sdwgt440zmx9k530afwj6gmq7q0lksh8lz2hPublished at
2023-06-07 18:11:17Event JSON
{
"id": "254ec12e11aa77d78c722e892b6fec186b092e5477e68778583c6b9b06a332b4",
"pubkey": "807351d851a3c419faea089fe59e0d72175abc5b316d48bfa974b48d83c07fed",
"created_at": 1686161477,
"kind": 1,
"tags": [
[
"e",
"47da86f112c9d7708a68cf185fffeef4ee890a05384ab56dcc3a7f4c5b99d2e2",
"",
"root"
],
[
"e",
"3288830a0f2e09b22863515bb963bd5e1d51e0b1e6f8394eb730586804c15e10",
"",
"reply"
],
[
"p",
"8caf4f6bf64d23daed998a9cb9803893f142d6edd68b94eca71e2ddb8d202a0f"
]
],
"content": "📅 Original date posted:2018-03-18\n📝 Original message: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.\n\n\nYes, I understand the additional cost but still thought it worthy of consideration.\n\n\nRegards,\n\nDamian Williamson\n\n________________________________\nFrom: Evan Klitzke \u003cevan at eklitzke.org\u003e\nSent: Sunday, 18 March 2018 4:50:34 PM\nTo: Damian Williamson; Bitcoin Protocol Discussion\nSubject: Re: [bitcoin-dev] feature: Enhance privacy by change obfuscation\n\n\nDamian Williamson via bitcoin-dev\n\u003cbitcoin-dev at lists.linuxfoundation.org\u003e writes:\n\u003e Operation: Provide a user selectable 'Enhanced privacy' option for\n\u003e transaction creation, when true the transaction randomly distributes\n\u003e change across up to twenty output addresses (minimum five?), provided\n\u003e each output is not dust.\n\nThis would be really expensive for the network due to the bloat in UTXO\nsize, a cost everyone has to pay for. Not to mention the fact that it\ndoesn't really seem that private, as the wallet is likely going to have\nto rejoin those inputs in future transactions (and the user will have to\npay a high transaction fee as a result).\n\n--\nEvan Klitzke\nhttps://eklitzke.org/\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180318/adae0170/attachment.html\u003e",
"sig": "a1648f3a0a013105862bea7df9ce3b37152ff7fd1b325867121c1e0d2d3a7bba09f39d84993ad3f1cdf47c78a848089031a6d7d4e0f1b63c977c141530a37317"
}