<oembed><type>rich</type><version>1.0</version><author_name>npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwet</author_name><author_url>https://nostr.ae/npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwet</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2018-05-17&#xA;📝 Original message:On Thu, May 17, 2018 at 3:25 PM, Matt Corallo via bitcoin-dev&#xA;&lt;bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&gt; I believe (1) could be skipped entirely - there is almost no reason why&#xA;&gt; you&#39;d not be able to filter for, eg, the set of output scripts in a&#xA;&gt; transaction you know about&#xA;&#xA;I think this is convincing for the txids themselves.&#xA;&#xA;What about also making input prevouts filter based on the scriptpubkey&#xA;being _spent_?  Layering wise in the processing it&#39;s a bit ugly, but&#xA;if you validated the block you have the data needed.&#xA;&#xA;This would eliminate the multiple data type mixing entirely.</html></oembed>