From 2da27d33c0e0c692503a62d13c59f2e8df59eb43 Mon Sep 17 00:00:00 2001 From: rating89us <45968869+rating89us@users.noreply.github.com> Date: Wed, 20 Jan 2021 20:57:14 +0100 Subject: [PATCH] ch08: outputs -> output --- ch08.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ch08.asciidoc b/ch08.asciidoc index b5e4f7bd..ad7636f3 100644 --- a/ch08.asciidoc +++ b/ch08.asciidoc @@ -270,7 +270,7 @@ Bloom filters are used to filter the transactions (and blocks containing them) t By checking against all these components, bloom filters can be used to match public key hashes, scripts, +OP_RETURN+ values, public keys in signatures, or any future component of a smart contract or complex script. -After a filter is established, the peer will then test each transaction's outputs against the bloom filter. Only transactions that match the filter are sent to the node. +After a filter is established, the peer will then test each transaction's output against the bloom filter. Only transactions that match the filter are sent to the node. In response to a +getdata+ message from the node, peers will send a +merkleblock+ message that contains only block headers for blocks matching the filter and a merkle path (see <>) for each matching transaction. The peer will then also send +tx+ messages containing the transactions matched by the filter.