Compact Block Relay (BIP 152)

Definition: Compact Block Relay (BIP 152) is a Bitcoin peer-to-peer (P2P) protocol for announcing and reconstructing blocks with less transmitted data than a full block. A compact-block message carries a block header, short IDs for most transactions, and a small set of full transactions. A compatible receiving node matches those IDs against transactions it already has, usually in its mempool, and requests anything it cannot reconstruct. The BIP is marked Deployed; it changes how peers relay block data, not the consensus rules that determine whether a block is valid.1

Date created BIP 152 was assigned on April 27, 2016; Bitcoin Core 0.13.0 release notes later announced support for the protocol.12
Protocol specification BIP 152
Directories Bitcoin Technology & Infrastructure

In-Depth Explanation

Why use compact blocks?

A node that receives a newly mined block may already have most of its transactions from earlier peer relay. Sending every transaction again in full creates avoidable network traffic and can cause brief bandwidth spikes. BIP 152 lets peers send compact identifiers for transactions likely to be known by the receiver, while still allowing the receiver to obtain any missing transaction data. Bitcoin Core’s 0.13.0 release notes describe reduced bandwidth spikes as the primary goal and lower propagation delay as a possible side effect.2

How a receiving node reconstructs a block

Peers first negotiate compact-block behavior with a sendcmpct message. The sender can then transmit a cmpctblock message containing the block header, six-byte short transaction IDs, and selected transactions in full. The coinbase transaction is normally prefilled, and other transactions may be prefilled when the sender expects a peer not to have them.1

The receiver calculates matching short IDs for transactions it already knows, usually from its mempool, and tries to place them into the block’s transaction order. If the reconstruction is complete, the node can process the reconstructed block through its normal validation path. If one or more transactions are absent or ambiguous, it can request the missing positions with getblocktxn and receive them in a blocktxn response. When compact reconstruction is not available or fails, peers can use ordinary block relay instead.1

Announcement modes and witness transactions

BIP 152 defines low- and high-bandwidth announcement modes. In high-bandwidth mode, a node may send compact-block announcements directly to a small number of selected peers, reducing a round trip when those peers can reconstruct the block immediately. Nodes can use the other mode to announce a block first and send compact data when requested. Neither mode guarantees that every peer will reconstruct the block without asking for more data.1

The specification also defines version 2 compact blocks for witness transactions. In that version, compact IDs use witness transaction IDs (wtxids), and the relayed transactions include witness data. This lets compatible peers reconstruct blocks that contain Segregated Witness transactions without confusing a transaction’s base serialization with its witness-inclusive form.1

Compact block relay is not compact block filtering

The similar names describe different jobs. BIP 152 helps full nodes relay a newly produced block to other peers. BIP 157 and BIP 158 specify client-side block filtering for light clients: BIP 157 defines a protocol for requesting and checking compact filters, while BIP 158 specifies a compact-filter format. Compact filters do not replace BIP 152’s block-propagation messages, and a compact-block message is not a wallet query filter.34

History

  • April 27, 2016: BIP 152 was assigned to specify compact blocks for Bitcoin peer-to-peer relay.1
  • Bitcoin Core 0.13.0: the release notes announced implementation of compact-block relay support. They identify lower bandwidth spikes as the main objective and faster propagation as a possible secondary effect.2
  • Current status: the Bitcoin BIPs index lists BIP 152 as Deployed. That status refers to the peer-services specification; it does not turn compact-block relay into a separate consensus rule.1

Limitations and Criticism

  • Bandwidth savings depend on how many transactions a receiving node already has. A different mempool or transaction-relay policy can leave it with more missing transactions to request.
  • Missing transactions require an additional message exchange, so compact relay is not always faster than receiving a complete block directly.
  • Short IDs are compact matching values, not full transaction hashes. The protocol accounts for possible collisions and reconstruction failures; an identifier match alone does not replace full block validation.1
  • Compact relay does not make a block smaller on Bitcoin’s consensus layer or guarantee propagation speed. It changes the peer-to-peer representation used while transferring block data.

Page updated: November 15, 2026.

Related Terms

Related Articles

CryptoGloss does not yet have an article focused on Bitcoin block relay. These broader articles cover connected topics: mining and block production, transaction ordering, cryptographic proof systems, and blockchain data storage.

See Also

Sources

  1. Matt Corallo, “BIP 152: Compact Block Relay,” Bitcoin Improvement Proposals, assigned April 27, 2016, status Deployed, https://github.com/bitcoin/bips/blob/master/bip-0152.mediawiki (accessed November 15, 2026).
  2. Bitcoin Core, “Bitcoin Core 0.13.0 Release Notes: Compact Block Support (BIP 152),” Bitcoin Core, https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-0.13.0.md (accessed November 15, 2026).
  3. Olaoluwa Osuntokun, Alex Akselrod, and Jim Posen, “BIP 157: Client Side Block Filtering,” Bitcoin Improvement Proposals, assigned May 24, 2017, status Deployed, https://github.com/bitcoin/bips/blob/master/bip-0157.mediawiki (accessed November 15, 2026).
  4. Olaoluwa Osuntokun and Alex Akselrod, “BIP 158: Compact Block Filters for Light Clients,” Bitcoin Improvement Proposals, assigned May 24, 2017, status Deployed, https://github.com/bitcoin/bips/blob/master/bip-0158.mediawiki (accessed November 15, 2026).