From 4ffad3f7c2fa51ca4766fe9b761c4048e67a943f Mon Sep 17 00:00:00 2001 From: clenser Date: Thu, 19 Oct 2023 15:36:53 +0000 Subject: [PATCH] Edited ch10_network.adoc with Atlas code editor --- ch10_network.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch10_network.adoc b/ch10_network.adoc index b8d7d3c9..acf314a9 100644 --- a/ch10_network.adoc +++ b/ch10_network.adoc @@ -802,7 +802,7 @@ helping lightweight clients find their transactions((("Bitcoin network", "bloom // https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-May/012636.html -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 bloom filter, each client hashes their addresses to create a bloom 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 lightweight client to download an 80-byte block header, a (usually) 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. === Lightweight Clients and Privacy