From: "Slurms MacKenzie" <slurms@gmx•us>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Making Electrum more anonymous
Date: Fri, 24 Jul 2015 05:42:07 +0200 [thread overview]
Message-ID: <trinity-61061d18-d667-4dd3-b87e-01880612c446-1437709327718@3capp-mailcom-bs10> (raw)
In-Reply-To: <55B1A254.6070806@voskuil.org>
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. 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. 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.
> Sent: Friday, July 24, 2015 at 4:26 AM
> From: "Eric Voskuil via bitcoin-dev" <bitcoin-dev@lists•linuxfoundation.org>
> To: "Stefan Richter" <richter@cs•rwth-aachen.de>, gb <kiwigb@yahoo•com>, "Thomas Voegtlin" <thomasv@electrum•org>
> Cc: bitcoin-dev@lists•linuxfoundation.org
> Subject: Re: [bitcoin-dev] Making Electrum more anonymous
>
>
> 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.
>
next prev parent reply other threads:[~2015-07-24 3:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 15:51 Thomas Voegtlin
2015-07-22 16:04 ` Natanael
2015-07-22 16:30 ` Eric Voskuil
2015-07-22 22:20 ` Eric Voskuil
2015-07-22 23:07 ` Joseph Gleason ⑈
2015-07-22 16:41 ` Joseph Gleason ⑈
2015-07-22 21:18 ` Mike Hearn
2015-07-22 23:11 ` gb
2015-07-23 0:07 ` Eric Voskuil
[not found] ` <114b2a76-ebc7-461a-b4bc-10873574d6c4@HUB2.rwth-ad.de>
2015-07-23 12:23 ` Stefan Richter
2015-07-24 2:26 ` Eric Voskuil
2015-07-24 3:42 ` Slurms MacKenzie [this message]
2015-07-24 4:44 ` Eric Voskuil
2015-07-24 9:38 ` Slurms MacKenzie
2015-07-24 11:12 ` s7r
2015-07-24 21:20 ` Slurms MacKenzie
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=trinity-61061d18-d667-4dd3-b87e-01880612c446-1437709327718@3capp-mailcom-bs10 \
--to=slurms@gmx$(echo .)us \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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