Message-ID: <55B1C2A2.6020704@voskuil.org>
Date: Thu, 23 Jul 2015 21:44:18 -0700
From: Eric Voskuil <eric@voskuil.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Slurms MacKenzie <slurms@gmx.us>, 
 bitcoin-dev@lists.linuxfoundation.org
References: <55AFBBE6.3060702@electrum.org>
	<1437606706.2688.0.camel@yahoo.com>	<114b2a76-ebc7-461a-b4bc-10873574d6c4@HUB2.rwth-ad.de>	<CAH+=Z+Xt4mja348Rg5Ot0u1VeCnVxm0wkVUA3GVgryZ4Yp4QNw@mail.gmail.com>,
	<55B1A254.6070806@voskuil.org>
	<trinity-61061d18-d667-4dd3-b87e-01880612c446-1437709327718@3capp-mailcom-bs10>
In-Reply-To: <trinity-61061d18-d667-4dd3-b87e-01880612c446-1437709327718@3capp-mailcom-bs10>
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="v0Kk3xFTmEJ2mD0dWUF78TPXB0gX2ACRA"
Subject: Re: [bitcoin-dev] Making Electrum more anonymous
Precedence: list

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--v0Kk3xFTmEJ2mD0dWUF78TPXB0gX2ACRA
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 07/23/2015 08:42 PM, Slurms MacKenzie via bitcoin-dev wrote:
>> From: "Eric Voskuil via bitcoin-dev"
>>
>> From our perspective, another important objective of query privacy is
>> allowing the caller make the trade-off between the relative levels of
>> privacy and performance - from absolute to non-existent. In some
>> cases privacy is neither required nor desired.
>>
>> Prefix filtering accomplishes the client-tuning objective. It also
>> does not suffer server collusion attacks nor is it dependent on
>> computational bounds. The primary trade-off becomes result set
>> (download) size against privacy.
>
> Keep in mind this is the similar premise as claimed to be offered by
> BIP37 bloom filters, but faulty assumptions and implementation
> failure in BitcoinJ have meant that bloom filters uniquely identify
> the wallet and offer no privacy for the user no matter what the
> settings are.

Yes, quite true. And without the ability to search using filters there
is no private restore from backup short of downloading the full chain,
rendering the idea rather pointless.

This is why privacy remains a significant issue. Privacy is an essential
aspect of fungibility. This is a central problem for Bitcoin. The
correlation of addresses within transactions is of course problematic.
Possibly zero knowledge proof will at some point come to the rescue. But
the correlation of addresses via search works against the benefits of
address non-reuse, and the correlation of addresses to IP addresses
works against the use of private addresses.

Solving the latter two problems can go a long way to reducing the impact
of the former. But currently the only solution is to run a full chain
wallet. This is not a viable solution for many scenarios, and getting
less so.

This is not a problem that can be ignored, nor is it unique to Electrum.
The Bloom filter approach was problematic, but that doesn't preclude the
existence of valid solutions.

> If you imagine a system where there is somehow complete
> separation and anonymization between all requests and subscriptions,
> the timing still leaks the association between the addresses to the
> listeners.

Well because of presumed relationship in time these are not actually
separated requests. Which is why even the (performance-unrealistic)
option of a distinct Tor route for each independent address request is
*still* problematic.

> The obvious solution to that is to use a very high latency
> mix network, but I somehow doubt that there's any desire for a wallet
> with SPV security that takes a week to return results.

Introducing truly-random timing variations into the mixnet solutions can
mitigate timing attacks, but yes, this just makes the already
intolerable performance problem much worse.

e


--v0Kk3xFTmEJ2mD0dWUF78TPXB0gX2ACRA
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJVscKiAAoJEDzYwH8LXOFOpQUH/Rxq8pCXwWuEjSFizC4A4J6O
506fqc/xbDDYHlzCiMlJY8FUAYuQl/7bCJ7Df40EYqByOxKPW6jxzksDqkB6bnGd
yoouHA56gm7BcxyTpIKYCfXzH/xhrdJcuzB6SAk7ll65HizZE1PqSa1hOL1Fkxmk
pEJjZjxPURL/ifvKw7EYL60rfc2GFkSRjbOALf31xxyjA0EKF+/zq6pW3yl2Eg0r
KBk1wYzO1Zxr/PXoJkK3CoSymGh3BT2woAmFWNJmmfBtnznPEyz2aqv2ngb7C1DL
rMF9Jfg0yRiW7hV0ROPxaKQCnmq0zbMxYkCFNa7u+UOetaQtji/m9oY809+H3fk=
=BDce
-----END PGP SIGNATURE-----

--v0Kk3xFTmEJ2mD0dWUF78TPXB0gX2ACRA--