From: Tom Zander <tomz@freedommail.ch>
To: Jonas Schnelli <dev@jonasschnelli.ch>,
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Date: Thu, 16 Feb 2017 16:10:46 +0100
Message-ID: <1853296.U0XO7RE0lo@strawberry>
In-Reply-To: <302c0b13-1951-faec-7266-f42bf748163d@jonasschnelli.ch>
References: <c949a1a2-ca6c-1fa8-6712-0846c5519f66@jonasschnelli.ch>
	<1850609.e9N5m2HcLf@strawberry>
	<302c0b13-1951-faec-7266-f42bf748163d@jonasschnelli.ch>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [bitcoin-dev] BIP150/151 concerns and some comments
Precedence: list

On Tuesday, 14 February 2017 22:01:51 CET Jonas Schnelli via bitcoin-dev=20
wrote:
> >> - If you use one of the todays available SPV clients, you will reveal
> >> your complete wallet content (=E2=80=9E~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.
> >=20
> > What about allowing trusted users connecting on a different connection.
> > Much like the RPC one.
> > Make that one encrypted. Different usecase, different connection.
>=20
> - What protocol would you use?

The RPC one. Which I think is JSON.

Your usecase is essentially just calling sendRawTransaction. Don=E2=80=99t=
=20
overcomplicate things.

=2D-=20
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel