Isidor Zeuner [ARCHIVE] on Nostr: š
Original date posted:2015-02-04 š Original message:Hi there, traditionally, ...
š
Original date posted:2015-02-04
š Original message:Hi there,
traditionally, the Bitcoin client strives to hide which output
addresses are change addresses going back to the payer. However,
especially with today's dynamically calculated miner fees, this
may often be ineffective:
A user sending a payment using the Bitcoin client will usually enter
the payment amount only up to the number of digits which are
considered to be significant enough. So, the least significant digits
will often be zero for the payment. With dynamically calculated miner
fees, this will often not be the case for the change amount, making it
easy for an observer to classify the output addresses.
A possible approach to handle this issue would be to add a randomized
offset amount to the payment amount. This offset amount can be small
in comparison to the payment amount.
Any thoughts?
Best regards,
Isidor
Published at
2023-06-07 15:29:34Event JSON
{
"id": "e342d2ccdbea84ae33086aaa54c85385b44aefdbd190c7181e53a839d1c358f2",
"pubkey": "70950d9ef527ee56cd47d1cec909c3ddfa69de32fbea13cad10641ee6dc93e39",
"created_at": 1686151774,
"kind": 1,
"tags": [
[
"e",
"1fef5faf1538d6047182d9bbac2eb6b0d5877ed37e90fddce7e55cdbf7edbd08",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "š
Original date posted:2015-02-04\nš Original message:Hi there,\n\ntraditionally, the Bitcoin client strives to hide which output\naddresses are change addresses going back to the payer. However,\nespecially with today's dynamically calculated miner fees, this\nmay often be ineffective:\n\nA user sending a payment using the Bitcoin client will usually enter\nthe payment amount only up to the number of digits which are\nconsidered to be significant enough. So, the least significant digits\nwill often be zero for the payment. With dynamically calculated miner\nfees, this will often not be the case for the change amount, making it\neasy for an observer to classify the output addresses.\n\nA possible approach to handle this issue would be to add a randomized\noffset amount to the payment amount. This offset amount can be small\nin comparison to the payment amount.\n\nAny thoughts?\n\nBest regards,\n\nIsidor",
"sig": "4f573295b2995df7a15cb6e513f6b6c61741251f5b427b003d6f001dea14aa038e7be6e081f22940f1c9e47cb54b1e83f3700882c9df9716c9080fce62c15ab7"
}