Inserts a transaction and merkle block filter into the peer, overwriting any existing filter.
This message installs a bloom filter into the peer. Subsequent INV notifications and MERKLEBLOCK messages only provide transactions that in match this bloom filter in some manner. The following items in a transaction are checked against the bloom filter:
If a filtered block is requested via in INV message, the installed bloom filter is used to choose which transactions are included in the response using the same matching algorithm as described above for transaction INVs.
|vector of bytes||up to 36000 bytes||bit vector||bloom filter data|
|num hash funcs||4 bytes||unsigned integer(LE)||number of hash functions used when generating this filter (max 50)|
|tweak||4 bytes||unsigned integer(LE)||arbitrary number that uniquifies this bloom filter|
|flags||1 byte||bit field||bloom filter flags|
The lowest two bits of flags control how the installed bloom filter is automatically updated. The remaining bits are reserved and should be set to 0.
|0||Do not update|
|2||update pay-to-pubkey, multi-sig, or check-lock-time-verify scripts only|