<oembed><type>rich</type><version>1.0</version><author_name>npub1e46n428mcyfwznl7nlsf6d3s7rhlwm9x3cmkuqzt3emmdpadmkaqqjxmcu</author_name><author_url>https://nostr.ae/npub1e46n428mcyfwznl7nlsf6d3s7rhlwm9x3cmkuqzt3emmdpadmkaqqjxmcu</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2018-05-17&#xA;📝 Original message:BIP 158 currently includes the following in the &#34;basic&#34; filter: 1)&#xA;txids, 2) output scripts, 3) input prevouts.&#xA;&#xA;I believe (1) could be skipped entirely - there is almost no reason why&#xA;you&#39;d not be able to filter for, eg, the set of output scripts in a&#xA;transaction you know about and (2) and (3) may want to be split out -&#xA;many wallets may wish to just find transactions paying to them, as&#xA;transactions spending from their outputs should generally be things&#xA;they&#39;ve created.&#xA;&#xA;In general, I&#39;m concerned about the size of the filters making existing&#xA;SPV clients less willing to adopt BIP 158 instead of the existing bloom&#xA;filter garbage and would like to see a further exploration of ways to&#xA;split out filters to make them less bandwidth intensive. Some further&#xA;ideas we should probably play with before finalizing moving forward is&#xA;providing filters for certain script templates, eg being able to only&#xA;get outputs that are segwit version X or other similar ideas.&#xA;&#xA;Matt</html></oembed>