From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <user@petertodd.org> Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 0FFEE10A3 for <bitcoin-dev@lists.linuxfoundation.org>; Thu, 17 May 2018 15:43:24 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from outmail149082.authsmtp.co.uk (outmail149082.authsmtp.co.uk [62.13.149.82]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 49343A3 for <bitcoin-dev@lists.linuxfoundation.org>; Thu, 17 May 2018 15:43:22 +0000 (UTC) Received: from mail-c245.authsmtp.com (mail-c245.authsmtp.com [62.13.128.245]) by punt22.authsmtp.com. (8.15.2/8.15.2) with ESMTP id w4HFhLmf020098; Thu, 17 May 2018 16:43:21 +0100 (BST) (envelope-from user@petertodd.org) Received: from petertodd.org (ec2-52-5-185-120.compute-1.amazonaws.com [52.5.185.120]) (authenticated bits=0) by mail.authsmtp.com (8.15.2/8.15.2) with ESMTPSA id w4HFhIXc094807 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 17 May 2018 16:43:20 +0100 (BST) (envelope-from user@petertodd.org) Received: from [127.0.0.1] (localhost [127.0.0.1]) by petertodd.org (Postfix) with ESMTPSA id 6AA454015E; Thu, 17 May 2018 15:43:18 +0000 (UTC) Received: by localhost (Postfix, from userid 1000) id E789D2112E; Thu, 17 May 2018 11:43:15 -0400 (EDT) Date: Thu, 17 May 2018 11:43:15 -0400 From: Peter Todd <pete@petertodd.org> To: Matt Corallo <lf-lists@mattcorallo.com>, Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org> Message-ID: <20180517154315.pcs6cmx3lx3on4dz@petertodd.org> References: <d43c6082-1b2c-c95b-5144-99ad0021ea6c@mattcorallo.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="xyibqxmf3hih2u5w" Content-Disposition: inline In-Reply-To: <d43c6082-1b2c-c95b-5144-99ad0021ea6c@mattcorallo.com> User-Agent: NeoMutt/20170113 (1.7.2) X-Server-Quench: 066c1c7c-59e9-11e8-a283-9cb654bb2504 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZIVwkA IjsJECJaVQIpKltL GxAVKBZePFsRUQkR aAdMdwUUFVQNAgsB Am4bWlJeVF57W2M7 bghPaBtcak9QXgdq T0pMXVMcUwEQd0R4 bk0eWx16dwIIfn14 bQhiWHYIXRd9Jlt4 SxtdCGwHMG99OWIX U11RJFFSdQcYLB1A alQxNiYHcQ5VPz4z GA41ejw8IwAXAgVt ClhQfRo8RUsbHzQ9 QxEeDH0mG0FNaSQ3 MxE8YmUdDkt5 X-Authentic-SMTP: 61633532353630.1039:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 52.5.185.120/25 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] BIP 158 Flexibility and Filter Size X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org> List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe> List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/> List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org> List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help> List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe> X-List-Received-Date: Thu, 17 May 2018 15:43:24 -0000 --xyibqxmf3hih2u5w Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 17, 2018 at 11:25:12AM -0400, Matt Corallo via bitcoin-dev wrot= e: > BIP 158 currently includes the following in the "basic" filter: 1) > txids, 2) output scripts, 3) input prevouts. >=20 > I believe (1) could be skipped entirely - there is almost no reason why > you'd not be able to filter for, eg, the set of output scripts in a > transaction you know about and (2) and (3) may want to be split out - > many wallets may wish to just find transactions paying to them, as > transactions spending from their outputs should generally be things > they've created. So I think we have two cases where wallets want to find txs spending from t= heir outputs: 1) Waiting for a confirmation 2) Detecting theft The former can be turned off once there are no expected unconfirmed transactions. As for the latter, this is probably a valuable thing for wallets to do. Mod= ulo reorgs, reducing the frequency that you check for stolen funds doesn't decr= ease total bandwidth cost - it's one filter match per block regardless - but per= haps the real-world bandwidth cost can be reduced by, say, waiting for a wifi connection rather than using cellular data. --=20 https://petertodd.org 'peter'[:-1]@petertodd.org --xyibqxmf3hih2u5w Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE0RcYcKRzsEwFZ3N5Lly11TVRLzcFAlr9ow4ACgkQLly11TVR LzeVXg/7BIyQOOrL77BDEakgmKSjIwLe0M23mMNmRqanO1yqK0ueEKmY+5LCyLu4 ZNGzy8S6/a8sDApI/FWq0EhsFgHEN0J9V7kjjQO49pAx3APP/JDz2IX4eAb/4pU8 f0T1OYnBgTdb0G/ankhBn/la7iZZGobuDsqwwB6ORBP3QPmIuZruUmigWxpdCfa3 Q/upfw1IXCBWq8e++ixGH/QJuj8yDIwzMjRNfcn8x3pAYhxPQbfqSFr5MhAawLvm Fph4Pz2i1odjBtyGgmcwAW+EUrLBBdKESc8yV9xs0AuACcOjVtaDi3VMJTqKc1Em EPKfnRPTJ4UhdQ35kAyZmenQIDAuPEQq9YYVh1gGIXHmLRzkBsu0gRZWLHDGaXtD PiRybVgsDT3wd5KBn5KGxajUPNWo524a6f/K9gUFFTyJFgUTmXM4Kob+9hVJA31i t2zdfz28HfDcyex6tNMRSoKwbHdkZJ+aIB8NGcoXi3U977Kop+9+513oObsOs2wM V9LR2rEKIYVjl4DHm74JTE8sedTuPCd2w7OWbhiNnElQBB4K6ZsQ/N0F6mC1Z1RZ TzX5Po52ZPpdvw6e0rpnSVAkC7Kg3NlPQaPhlIrt3hInB+i5E3Jc5ndgpldECxuM vhRZZ8KWP0OAOsZ4jfcCcuo5nCsgyvltLF0dO7wf0MxlysF0OfE= =reII -----END PGP SIGNATURE----- --xyibqxmf3hih2u5w--