Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 41616B1E for ; Mon, 19 Jun 2017 16:00:08 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from blaine.gmane.org (unknown [195.159.176.226]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id B9B3A212 for ; Mon, 19 Jun 2017 16:00:07 +0000 (UTC) Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1dMz5p-0005sU-T6 for bitcoin-dev@lists.linuxfoundation.org; Mon, 19 Jun 2017 17:59:57 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: bitcoin-dev@lists.linuxfoundation.org From: Andreas Schildbach Date: Mon, 19 Jun 2017 17:59:57 +0200 Message-ID: References: <537fb7106e0387c77537f0b1279cbeca@cock.lu> <55482016.LADLl5KXAH@strawberry> <4052F361-966C-4817-9779-146D4B43D1FE@jonasschnelli.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@blaine.gmane.org User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 In-Reply-To: <4052F361-966C-4817-9779-146D4B43D1FE@jonasschnelli.ch> Content-Language: en-US X-Spam-Status: No, score=2.0 required=5.0 tests=BAYES_00,DKIM_ADSP_ALL, FORGED_MUA_MOZILLA,RDNS_NONE autolearn=no version=3.3.1 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] BIP Proposal: Compact Client Side Filtering for Light Clients 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: Mon, 19 Jun 2017 16:00:08 -0000 On 06/19/2017 05:49 PM, Jonas Schnelli via bitcoin-dev wrote: >>> It's been debated if [filtering of] unconfirmed transactions are >>> necessary, >> >> Why would it not be needed? Any SPV client (when used as a payment-receiver) >> requires this from a simple usability point of view. > > > I think many users would be willing ... > a) … to trade higher privacy (using client side filtering) for not having the „incoming transaction“ feature > b) – if they want 0-conf – to fetch all inved transactions Another number: I'm answering dozens of support inquiries about delayed/missing transactions per day. Over the 7 years of Bitcoin Wallet's existence, I estimate about 50000 inquiries. On the other hand, I remember only 1 (one) inquiry about the privacy problems of BIP37 (or privacy at all). From a regular user's point of view, privacy is non-issue. Sure, everyone would take it for free, but certainly not if it a) delays incoming payments or b) quickly eats up your traffic quota.