š
Original date posted:2015-05-10
š Original message:That's a lot of work, a lot of extra utxo's, and a lot of blockchain spam, just
so I can do a convoluted form of arithmetic on my balance.
If a tx contained an explicit miner fee and a change address, but did not
compute the change, letting the network compute it (and therefore merge
transactions spending the same utxo), could one add some form of ring signature
a la Dash to alleviate the worsened privacy implications?
Jeff Garzik [jgarzik at bitpay.com] wrote:
> This has been frequently explored on IRC.
>
> My general conclusion is "dollar bills" - pick highly common denominations of
> bitcoins.Ā Aggregate to obtain these denominations, but do not aggregate
> further.
>
> This permits merge avoidance (privacy++), easy coinjoin where many hide in the
> noise (privacy++), wallet dust de-fragmentation, while avoiding the
> over-aggregation problem where you have consolidated down to one output.
>
> Thus a wallet would have several consolidation targets.
>
> Another strategy is simply doubling outputs.Ā Say you pay 0.1 BTC to
> Starbucks.Ā Add another 0.1 BTC output to yourself, and a final change output.Ā
> Who can say which output goes to Starbucks?
>
> There are many iterations and trade-offs between fragmentation and privacy.
--
Cheers, Bob McElrath
"The individual has always had to struggle to keep from being overwhelmed by
the tribe. If you try it, you will be lonely often, and sometimes frightened.
But no price is too high to pay for the privilege of owning yourself."
-- Friedrich Nietzsche
Bob McElrath [ARCHIVE] /
npub15nā¦8vrz4
2023-06-07 15:34:27
in reply to nevent1qā¦yf70
Author Public Key
npub15n7zls4lcps7wksmdctal39neyact74jljgsq86ylkzfn4njk95sv8vrz4Published at
2023-06-07 15:34:27Event JSON
{
"id": "cdd48b81eaaea82402c4c19d7aa544588cbd7dfc303863355d46fc82e3255314",
"pubkey": "a4fc2fc2bfc061e75a1b6e17dfc4b3c93b85fab2fc91001f44fd8499d672b169",
"created_at": 1686152067,
"kind": 1,
"tags": [
[
"e",
"e436370a47825fa52c60553290bd211115ae129df3a23920b2899f508d96bf5e",
"",
"root"
],
[
"e",
"243d258a905b126073050034402f1c04f08bc5bb6b9240d417a44dc1e8b85608",
"",
"reply"
],
[
"p",
"b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11"
]
],
"content": "š
Original date posted:2015-05-10\nš Original message:That's a lot of work, a lot of extra utxo's, and a lot of blockchain spam, just\nso I can do a convoluted form of arithmetic on my balance.\n\nIf a tx contained an explicit miner fee and a change address, but did not\ncompute the change, letting the network compute it (and therefore merge\ntransactions spending the same utxo), could one add some form of ring signature\na la Dash to alleviate the worsened privacy implications?\n\nJeff Garzik [jgarzik at bitpay.com] wrote:\n\u003e This has been frequently explored on IRC.\n\u003e \n\u003e My general conclusion is \"dollar bills\" - pick highly common denominations of\n\u003e bitcoins.Ā Aggregate to obtain these denominations, but do not aggregate\n\u003e further.\n\u003e \n\u003e This permits merge avoidance (privacy++), easy coinjoin where many hide in the\n\u003e noise (privacy++), wallet dust de-fragmentation, while avoiding the\n\u003e over-aggregation problem where you have consolidated down to one output.\n\u003e \n\u003e Thus a wallet would have several consolidation targets.\n\u003e \n\u003e Another strategy is simply doubling outputs.Ā Say you pay 0.1 BTC to\n\u003e Starbucks.Ā Add another 0.1 BTC output to yourself, and a final change output.Ā \n\u003e Who can say which output goes to Starbucks?\n\u003e \n\u003e There are many iterations and trade-offs between fragmentation and privacy.\n\n\n\n--\nCheers, Bob McElrath\n\n\"The individual has always had to struggle to keep from being overwhelmed by\nthe tribe. If you try it, you will be lonely often, and sometimes frightened.\nBut no price is too high to pay for the privilege of owning yourself.\" \n -- Friedrich Nietzsche",
"sig": "fba1c8117a441e493346f1747d8f40870b9efaeba692bf7ae0864ce4882d5743727b0737e080bff2c59eeb36a2836971dcc2f2c817be66e6b4e45c3ed088ef04"
}