mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2025-03-25 11:55:44 +00:00
CH10: SPV privacy: update to account for compact block filters too
Previously assumed bloom filters would be used. Only small updates needed.
This commit is contained in:
parent
1e2a2252b3
commit
8b09a51b7b
@ -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.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user