{"type":"rich","version":"1.0","author_name":"npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2","author_url":"https://nostr.ae/npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2018-05-17\n📝 Original message:On Thu, May 17, 2018 at 11:25:12AM -0400, Matt Corallo via bitcoin-dev wrote:\n\u003e BIP 158 currently includes the following in the \"basic\" filter: 1)\n\u003e txids, 2) output scripts, 3) input prevouts.\n\u003e \n\u003e I believe (1) could be skipped entirely - there is almost no reason why\n\u003e you'd not be able to filter for, eg, the set of output scripts in a\n\u003e transaction you know about and (2) and (3) may want to be split out -\n\u003e many wallets may wish to just find transactions paying to them, as\n\u003e transactions spending from their outputs should generally be things\n\u003e they've created.\n\nSo I think we have two cases where wallets want to find txs spending from their\noutputs:\n\n1) Waiting for a confirmation\n2) Detecting theft\n\nThe former can be turned off once there are no expected unconfirmed\ntransactions.\n\nAs for the latter, this is probably a valuable thing for wallets to do. Modulo\nreorgs, reducing the frequency that you check for stolen funds doesn't decrease\ntotal bandwidth cost - it's one filter match per block regardless - but perhaps\nthe real-world bandwidth cost can be reduced by, say, waiting for a wifi\nconnection rather than using cellular data.\n\n-- \nhttps://petertodd.org 'peter'[:-1]@petertodd.org\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 833 bytes\nDesc: not available\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180517/7732ad90/attachment-0001.sig\u003e"}