From: Tom Zander <tomz@freedommail.ch>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP150/151 concerns and some comments
Date: Tue, 14 Feb 2017 19:01:03 +0100 [thread overview]
Message-ID: <1850609.e9N5m2HcLf@strawberry> (raw)
In-Reply-To: <c949a1a2-ca6c-1fa8-6712-0846c5519f66@jonasschnelli.ch>
On Tuesday, 14 February 2017 17:10:15 CET Jonas Schnelli via bitcoin-dev
wrote:
> - If you use one of the todays available SPV clients, you will reveal
> your complete wallet content („~all your addresses") to every network
> observer between you and the node you have connected to. This means, if
> you pay for a coffee (while being on the owners WIFI), the coffee owner
> and all the involved ISPs can correlate your wallet with your other
> internet behavior. Same is true for your cellphone provider if you use
> cellular.
What about allowing trusted users connecting on a different connection. Much
like the RPC one.
Make that one encrypted. Different usecase, different connection.
--
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel
next prev parent reply other threads:[~2017-02-14 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 16:10 [bitcoin-dev] BIP150/151 concerns and some comments Jonas Schnelli
2017-02-14 18:01 ` Tom Zander [this message]
2017-02-14 21:01 ` Jonas Schnelli
2017-02-16 15:10 ` Tom Zander
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=1850609.e9N5m2HcLf@strawberry \
--to=tomz@freedommail.ch \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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