Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.149.58 as permitted sender)
	client-ip=62.13.149.58; envelope-from=pete@petertodd.org;
	helo=outmail149058.authsmtp.co.uk; 
Date: Thu, 5 Feb 2015 17:17:26 -0800
From: Peter Todd <pete@petertodd.org>
To: Isidor Zeuner <cryptocurrencies@quidecco.de>
Message-ID: <20150206011726.GJ32226@muck>
References: <20150204142323.DEC4BE2DCDE@quidecco.de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="lqaZmxkhekPBfBzr"
Content-Disposition: inline
In-Reply-To: <20150204142323.DEC4BE2DCDE@quidecco.de>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] determining change addresses using the
 least significant digits
Precedence: list


--lqaZmxkhekPBfBzr
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Feb 04, 2015 at 03:23:23PM +0100, Isidor Zeuner wrote:
> Hi there,
>=20
> 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:
>=20
> 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.
>=20
> 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.
>=20
> Any thoughts?

Have you looked at Armory? IIRC they do this kind of stuff.

--=20
'peter'[:-1]@petertodd.org
0000000000000000165ecbd638ec09226f84c34d3d775d34ca5df4abfa8cb57c

--lqaZmxkhekPBfBzr
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----

iQGrBAEBCACVBQJU1BYiXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAxNjVlY2JkNjM4ZWMwOTIyNmY4NGMzNGQzZDc3NWQzNGNh
NWRmNGFiZmE4Y2I1N2MvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkfs4xQf6A/0e97srNMB/R6jQNDOPchV8
mCK+yqIVou60QGyklxkXUN1EW/b60pyd8KwFnWcnvVkNacGseMu5xoel9ZmqAyel
sV8nZf3e0dhZdbhG/nij36z3DqbbmHREYSNl6p42d4uJ/TFCuTfYkLUiz2a9AgE3
GwVlhedyIIhoQN+aEu2Vqdv9Z/pNMSrIKv1rTN1OtC2DRQ0JybguUCLxwEqE+YoW
8qBoaywjnWcJ4d4bpU8wbFRkbyB+XfXfd7jRpr0/2rP78N3TLFVRiKUAD0yqdOKT
iBYaBlS1jXyzYPvyqTQmLCjMBCbhuXLembtF50yxoQH1lrKHiz4dZAp4RjGajQ==
=GwFK
-----END PGP SIGNATURE-----

--lqaZmxkhekPBfBzr--