From 8b09a51b7bf10743dd522e972c97d84909c1132d Mon Sep 17 00:00:00 2001 From: "David A. Harding" Date: Thu, 18 May 2023 14:05:21 -1000 Subject: [PATCH] CH10: SPV privacy: update to account for compact block filters too Previously assumed bloom filters would be used. Only small updates needed. --- ch08.asciidoc | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/ch08.asciidoc b/ch08.asciidoc index 3bf2f964..43c0ac46 100644 --- a/ch08.asciidoc +++ b/ch08.asciidoc @@ -1132,16 +1132,15 @@ the best possible privacy should still use their own full node. === SPV Clients and Privacy Clients that implement SPV have weaker privacy than a full node. A full -node receives all transactions and therefore reveals no information +node downloads all transactions and therefore reveals no information about whether it is using some address in its wallet. An SPV client -receives a filtered list of transactions related to the addresses that -are in its wallet. As a result, it reduces the privacy of the owner. +only downloads transactions that are related to its wallet in some way. -Bloom filters are a way to reduce the loss of privacy. Without them, an +Bloom filters and compact block filters are a way to reduce the loss of privacy. Without them, an SPV client would have to explicitly list the addresses it was interested -in, creating a serious breach of privacy. However, even with bloom +in, creating a serious breach of privacy. However, even with filters, an adversary monitoring the traffic of an SPV client or -connected to it directly as a node in the P2P network can collect enough +connected to it directly as a node in the P2P network may be able to collect enough information over time to learn the addresses in the wallet of the SPV client.