Response: Thin Block (“thinblock”)

Response: Thin Block (“thinblock”)

This message delivers an thinblock to the remote peer.
The thinblock starts with the block header, followed by the hashes of all the transactions in the block.
The transaction hashes are in the same order as they are in the actual block.
All the transactions that are in the block, but not matched by the Bloom filter included in the previous get_xthin message should be appended, which should include at least the coinbase transaction.


Field Length Format Description
Block header 80 bytes block header The header of the block transmitted.
Transaction hashes # of tx * 32 bytes vector The hashes of all the transactions included in the block.
Missing transactions variable vector Transactions that are included in the blocks but are not matched by the Bloom filter.