Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id D6466B5F for ; Tue, 14 Feb 2017 17:58:39 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mx-out02.mykolab.com (mx.kolabnow.com [95.128.36.1]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id EED5814D for ; Tue, 14 Feb 2017 17:58:38 +0000 (UTC) X-Virus-Scanned: amavisd-new at kolabnow.com X-Spam-Score: -2.9 X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 Received: from mx03.mykolab.com (mx03.mykolab.com [10.20.7.101]) by mx-out02.mykolab.com (Postfix) with ESMTPS id B5FB261778 for ; Tue, 14 Feb 2017 18:58:35 +0100 (CET) From: Tom Zander To: Bitcoin Protocol Discussion Date: Tue, 14 Feb 2017 19:01:03 +0100 Message-ID: <1850609.e9N5m2HcLf@strawberry> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Tue, 14 Feb 2017 18:01:41 +0000 Subject: Re: [bitcoin-dev] BIP150/151 concerns and some comments X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Feb 2017 17:58:39 -0000 On Tuesday, 14 February 2017 17:10:15 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 net= work > 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. Muc= h=20 like the RPC one. Make that one encrypted. Different usecase, different connection. =2D-=20 Tom Zander Blog: https://zander.github.io Vlog: https://vimeo.com/channels/tomscryptochannel