public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Isidor Zeuner <cryptocurrencies@quidecco.de>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] determining change addresses using the least significant digits
Date: Wed,  4 Feb 2015 15:23:23 +0100 (CET)	[thread overview]
Message-ID: <20150204142323.DEC4BE2DCDE@quidecco.de> (raw)

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



             reply	other threads:[~2015-02-04 14:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04 14:23 Isidor Zeuner [this message]
2015-02-06  1:17 ` [Bitcoin-development] determining change addresses using the least significant digits Peter Todd
2015-02-06  3:16 ` Justus Ranvier
2015-02-06  4:08   ` [Bitcoin-development] [SPAM] " Luke Dashjr
2015-02-06 10:11 ` [Bitcoin-development] " Wladimir
2015-02-06 15:08   ` Jeff Garzik
2015-02-06 17:50     ` Justus Ranvier
2015-02-06 18:21 ` Gregory Maxwell

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=20150204142323.DEC4BE2DCDE@quidecco.de \
    --to=cryptocurrencies@quidecco.de \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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