Ancestor Package Relay (BIP 331)

Definition: Ancestor Package Relay is a draft Bitcoin peer-to-peer protocol proposal in BIP 331. It describes messages that let nodes request information about an unconfirmed transaction’s ancestors and download related transactions in batches. Relaying transactions as a package can help peers assess a low-fee parent together with a higher-fee child, and can improve recovery of transactions whose parents have not yet arrived. Bitcoin Core currently documents limited one-parent-one-child package relay; that is not the same as full deployment of the broader BIP 331 protocol.123

Proposal Read BIP 331 · Status: Draft
Current Core support Limited one-parent-one-child package relay is documented; broader ancestor package relay remains further work.
Directories Bitcoin Technology & Infrastructure

What counts as a package

In Bitcoin transaction policy, a package is a group of related, unconfirmed transactions considered together. A child transaction spends an output of its parent; that parent may itself have an unconfirmed ancestor. A node can evaluate the combined fee and size of a package instead of deciding from each transaction in isolation. This matters when a parent pays a low fee but a descendant adds enough fee to make including both transactions attractive. The package rules are still constrained by each node’s acceptance policy and by the miners’ transaction-selection decisions.1

What BIP 331 proposes

BIP 331 describes a peer negotiation and download flow. During a connection handshake, peers can signal which package-relay message types they support. One part lets a node request ancestor-package information for a transaction, so it can learn which unconfirmed transactions are needed. Another part allows a group of transaction data to be downloaded in a batch rather than requiring a separate request round for every missing parent. The BIP also describes how peers could handle orphan transactions—transactions received before their parents—without announcing packages unsolicited to every peer.1

The proposal addresses two related propagation cases. First, a high-feerate child may arrive before its low-feerate parent; a peer can request the missing ancestor information and evaluate the package together. Second, when a transaction is an orphan, the receiver can ask for the relevant ancestor set and retrieve the dependent transactions in one batch. The protocol is receiver-initiated and only used when both peers negotiate the relevant support. It is designed to reduce unnecessary round trips and help peers maintain compatible views of transactions likely to be mined together.1

How it differs from CPFP and submitpackage

Child Pays for Parent (CPFP) is a fee-bumping technique: the child transaction pays a higher fee so a miner evaluating the pair has an incentive to include the parent too. Package relay is about how nodes communicate and evaluate related unconfirmed transactions across peer connections. It can support CPFP-style use cases, but the terms are not interchangeable. Bitcoin Core’s submitpackage RPC is a local interface for submitting packages to a node; it is also distinct from a complete peer-to-peer protocol for requesting ancestor information and batches.23

Implementation status and limits

BIP 331 remains Draft in the BIP repository. Bitcoin Core has developed narrower package-relay behavior that uses existing transaction-relay mechanisms for one-parent-one-child packages. Core’s v28.0 notes describe opportunistically pairing a low-feerate transaction with its child, and v31.0 notes describe extending that behavior to some packages whose parent is below the minimum relay feerate, including a zero-fee parent. These features do not establish that the full BIP 331 ancestor-info and batch-download protocol is deployed across the network. Bitcoin Core’s package-relay tracker lists ancestor package relay as further work, including more complex package topologies and orphan handling.234

Even with package support, relay is not confirmation. A node can reject a package for policy or resource reasons; peers may not support the same mechanisms; and miners can choose which transactions to include. Applications that rely on fee bumps need to handle the specific wallet, node, and mining policies available to them rather than assuming a package will propagate everywhere.

History

  • August 8, 2022: BIP 331 was assigned as a draft peer-services specification for ancestor package relay.1
  • Bitcoin Core v28.0: Release notes described limited one-parent-one-child relay using existing transaction-relay messages, including an opportunistic path for low-fee parents paired with children.2
  • Bitcoin Core v31.0: Release notes expanded the limited one-parent-one-child behavior to include packages with a parent below minimum relay feerate, while the project tracker continued to list broader ancestor-package relay as further work.34

Last updated: November 13, 2026.

Criticisms

  • The BIP remains a draft, so its proposed messages and wider network support should not be described as a universally deployed feature.
  • Package acceptance remains bounded by node policy, resource limits, and package shape; relay support does not guarantee mining or confirmation.
  • Implementing package protocols adds complexity to peer negotiation, validation, download behavior, and denial-of-service protections.
  • Users may encounter different behavior across wallet, node, and service implementations. Fee-bumping designs need fallbacks for peers that do not support the same package behavior.

Related Terms

Related Articles

See Also

Sources

  1. Zhao, Gloria. “BIP 331: Ancestor Package Relay.” Bitcoin Improvement Proposals. Assigned August 8, 2022. Accessed November 13, 2026. https://github.com/bitcoin/bips/blob/master/bip-0331.mediawiki.
  2. Bitcoin Core. “Bitcoin Core 28.0 Release Notes.” Bitcoin Core. Accessed November 13, 2026. https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-28.0.md.
  3. Bitcoin Core. “Bitcoin Core 31.0 Release Notes.” Bitcoin Core. Accessed November 13, 2026. https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-31.0.md.
  4. Bitcoin Core. “Package Relay Project Tracking.” Issue #27463. Accessed November 13, 2026. https://github.com/bitcoin/bitcoin/issues/27463.