{"type":"rich","version":"1.0","author_name":"npub19helcfnqgk2jrwzjex2aflq6jwfc8zd9uzzkwlgwhve7lykv23mq5zkvn4","author_url":"https://nostr.ae/npub19helcfnqgk2jrwzjex2aflq6jwfc8zd9uzzkwlgwhve7lykv23mq5zkvn4","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2018-05-18\n📝 Original message:Greg wrote:\n\u003e What about also making input prevouts filter based on the scriptpubkey\nbeing\n\u003e _spent_?  Layering wise in the processing it's a bit ugly, but if you\n\u003e validated the block you have the data needed.\n\nAFAICT, this would mean that in order for a new node to catch up the filter\nindex (index all historical blocks), they'd either need to: build up a\nutxo-set in memory during indexing, or would require a txindex in order to\nlook up the prev out's script. The first option increases the memory load\nduring indexing, and the second requires nodes to have a transaction index\n(and would also add considerable I/O load). When proceeding from tip, this\ndoesn't add any additional load assuming that your synchronously index the\nblock as you validate it, otherwise the utxo set will already have been\nupdated (the spent scripts removed).\n\nI have a script running to compare the filter sizes assuming the regular\nfilter switches to include the prev out's script rather than the prev\noutpoint itself. The script hasn't yet finished (due to the increased I/O\nload to look up the scripts when indexing), but I'll report back once it's\nfinished.\n\n-- Laolu\n\n\nOn Thu, May 17, 2018 at 9:37 AM Gregory Maxwell via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e On Thu, May 17, 2018 at 3:25 PM, Matt Corallo via bitcoin-dev\n\u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \u003e I believe (1) could be skipped entirely - there is almost no reason why\n\u003e \u003e you'd not be able to filter for, eg, the set of output scripts in a\n\u003e \u003e transaction you know about\n\u003e\n\u003e I think this is convincing for the txids themselves.\n\u003e\n\u003e What about also making input prevouts filter based on the scriptpubkey\n\u003e being _spent_?  Layering wise in the processing it's a bit ugly, but\n\u003e if you validated the block you have the data needed.\n\u003e\n\u003e This would eliminate the multiple data type mixing entirely.\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180518/228dc08e/attachment.html\u003e"}