An idea was posted to the Bitcoin-Dev mailing list by an anonymous
An idea was ((("Bitcoin network", "compact block filters", id="bitcoin-network-compact-filter")))((("compact block filters", id="compact-block-filter")))((("blocks", "compact block filters", id="block-compact-filter")))posted to the Bitcoin-Dev mailing list by an anonymous
developer in 2016 of reversing the bloom filter process. With a BIP37
developer in 2016 of reversing the bloom filter process. With a BIP37
bloom filter, each client hashes their addresses to create a bloom
bloom filter, each client hashes their addresses to create a bloom
filter and nodes hash parts of each transaction to attempt to match
filter and nodes hash parts of each transaction to attempt to match
@ -1107,7 +1107,7 @@ would calculate the filter for each block themselves and only accept a
block if it contained an accurate commitment. That would allow a
block if it contained an accurate commitment. That would allow a
lightweight client to download an 80-byte block header, a (usually)
lightweight client to download an 80-byte block header, a (usually)
small coinbase transaction, and the filter for that block to receive
small coinbase transaction, and the filter for that block to receive
strong evidence that the filter was accurate.
strong evidence that the filter ((("Bitcoin network", "compact block filters", startref="bitcoin-network-compact-filter")))((("compact block filters", startref="compact-block-filter")))((("blocks", "compact block filters", startref="block-compact-filter")))was accurate.