mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2024-11-25 17:38:26 +00:00
Edited ch10_network.adoc with Atlas code editor
This commit is contained in:
parent
b3d7e4d3e0
commit
63893628b0
@ -942,7 +942,7 @@ application of Bitcoin ((("Bitcoin network", "compact block filters", "GCS (Golo
|
||||
|
||||
==== What Data to Include in a Block Filter
|
||||
|
||||
Our primary goal is to allow wallets to learn whether a block contains a
|
||||
Our primary ((("Bitcoin network", "compact block filters", "what to include", id="bitcoin-network-compact-filter-include")))((("compact block filters", "what to include", id="compact-block-filter-include")))((("blocks", "compact block filters", "what to include", id="block-compact-filter-include")))goal is to allow wallets to learn whether a block contains a
|
||||
transaction affecting that wallet. For a wallet to be effective, it
|
||||
needs to learn two types of information:
|
||||
|
||||
@ -1002,7 +1002,7 @@ But a block itself doesn't include the output scripts from transactions
|
||||
included in previous blocks, so there's no convenient way for a client
|
||||
to verify a block filter was built correctly. However, there is an
|
||||
alternative that can help a client detect if a peer is lying to it:
|
||||
obtaining the same filter from multiple peers.
|
||||
obtaining the same filter from ((("Bitcoin network", "compact block filters", "what to include", startref="bitcoin-network-compact-filter-include")))((("compact block filters", "what to include", startref="compact-block-filter-include")))((("blocks", "compact block filters", "what to include", startref="block-compact-filter-include")))multiple peers.
|
||||
|
||||
==== Downloading Block Filters from Multiple Peers
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user