Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.223.176 as permitted sender)
	client-ip=209.85.223.176; envelope-from=laanwj@gmail.com;
	helo=mail-ie0-f176.google.com; 
MIME-Version: 1.0
In-Reply-To: <20150204142323.DEC4BE2DCDE@quidecco.de>
References: <20150204142323.DEC4BE2DCDE@quidecco.de>
Date: Fri, 6 Feb 2015 10:11:28 +0000
Message-ID: <CA+s+GJCMqcfj+1dALUQyepo=Y3Fk=QWTp5fnmR53VAkOf=3Bwg@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Isidor Zeuner <cryptocurrencies@quidecco.de>
Content-Type: text/plain; charset=UTF-8
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] determining change addresses using the
 least significant digits
Precedence: list

On Wed, Feb 4, 2015 at 2:23 PM, Isidor Zeuner
<cryptocurrencies@quidecco.de> wrote:

> 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?

Adding/subtracting a randomized offset amount is one way, but there
have also been more sophisticated ideas to obfuscate the amount, e.g.
by adding multiple change outputs or even distributing over multiple
transactions (potentially coinjoined for further privacy).

Mike Hearn had some ideas regarding obfuscation of payment amounts,
which still make sense, and he wrote about them here:
https://medium.com/@octskyward/merge-avoidance-7f95a386692f

Wladimir