Child Pays for Parent (CPFP) is a Bitcoin fee-bumping method in which a wallet creates a higher-fee child transaction that spends an output of a lower-fee, unconfirmed parent. When a miner or node evaluates the transactions as a package, the child’s fee can raise the package’s average fee rate and make including both more attractive. The parent remains unchanged. 13
| Package-relay proposal | BIP 331, a draft proposal for ancestor package relay, was assigned on August 8, 2022. 3 |
|---|---|
| Bitcoin Core support | Bitcoin Core 28.0 notes |
| Package policy | Bitcoin Core package policy |
| Directory | Bitcoin Directory |
How CPFP works
Bitcoin transactions can spend outputs created by earlier transactions. If a parent is waiting with a low fee rate, a wallet that controls a spendable parent output can create a child transaction and attach a larger fee to it. A miner that considers the parent and child together may find their combined fee rate competitive even when the parent’s fee rate alone is not. Package-aware node policies can also evaluate related transactions together, but acceptance and relay depend on the wallet, node software, and the package rules in use. 13
A simplified example shows the arithmetic:
| Transaction | Size | Fee |
|---|---|---|
| Low-fee parent | 200 vB | 200 satoshis |
| CPFP child | 100 vB | 1,400 satoshis |
| Combined package | 300 vB | 1,600 satoshis, or about 5.33 sat/vB |
This example treats the parent and child as one package: total fees divided by total virtual size. Actual selection depends on the transactions, mempool conditions, and miner or node policy; a calculated package rate is not a promise of confirmation.
Who can use it
The child must spend an output that is available and spendable. A recipient may sometimes use CPFP on an incoming payment if their wallet supports spending an unconfirmed output; a sender may use it on a change output. The person creating the child needs access to the relevant spending key or signing process and must be able to pay the child’s fee. If no suitable output is available, or the wallet refuses to spend it before confirmation, CPFP may not be an option.
CPFP is often useful when the original sender cannot or does not replace the parent directly. It can also be combined conceptually with other fee-management approaches, but it is distinct from Replace-by-Fee (RBF): RBF broadcasts a conflicting replacement transaction, while CPFP leaves the parent in place and adds a dependent child. Bitcoin Core’s package relay and acceptance support is limited to particular package shapes and rules; it should not be assumed that every multi-transaction package will propagate across the network. 124
Limits and trade-offs
CPFP can require the recipient or another output owner to spend funds and pay a fee they did not initially expect. The child fee must be large enough to raise the package’s incentive for inclusion, and transaction chains are subject to node limits. A parent may already be confirmed, the output may be unspendable, or package relay may not be supported along the route to a miner. In those cases, the child may not help the parent confirm sooner.
CPFP does not change Bitcoin’s consensus rules, bypass transaction validation, or guarantee a place in the next block. It changes the economic incentives around a set of linked transactions. Users should verify the child’s inputs, outputs, and total fee in their wallet before signing.
History
- Bitcoin Core v0.13 onward — Bitcoin Core’s package-relay proposal notes that mempool and block selection have used ancestor-package fee rates since v0.13, allowing higher-fee descendants to affect the incentive to include their ancestors. 3
- 2022 — BIP 331, “Ancestor Package Relay,” was assigned as a draft to propose peer-to-peer messages for requesting and relaying unconfirmed ancestor packages. It describes CPFP as one way users can raise transaction priority. 3
- 2024 — Bitcoin Core 28.0 release notes describe limited 1-parent/1-child package relay for transactions with low fee rates. The notes caution that the peer-to-peer feature is limited and not yet reliable under adversarial conditions. 4
Related Terms
Related Articles
- What Happens to Bitcoin Mining Rewards After New BTC Issuance Ends?
- Bitcoin as Collateral: Bank Loans, Mortgages, and DeFi Explained
- What the 2024 U.S. Spot Bitcoin ETP Launch Changed—and What It Didn’t
- Why Bitcoin Can Move With Stocks—and Why Correlation Changes
See Also
Page updated: November 10, 2026.
Sources
- Bitcoin Core Developers. “Package Mempool Accept.” Bitcoin Core documentation. GitHub. Accessed November 10, 2026. https://github.com/bitcoin/bitcoin/blob/master/doc/policy/packages.md.
- Bitcoin Core Developers. “Mempool Replacements.” Bitcoin Core documentation. GitHub. Accessed November 10, 2026. https://github.com/bitcoin/bitcoin/blob/master/doc/policy/mempool-replacements.md.
- Bitcoin Improvement Proposals. “BIP 331: Ancestor Package Relay.” Assigned August 8, 2022. Status: Draft. Accessed November 10, 2026. https://github.com/bitcoin/bips/blob/master/bip-0331.mediawiki.
- Bitcoin Core Developers. “Bitcoin Core 28.0 Release Notes.” GitHub. Accessed November 10, 2026. https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-28.0.md.
- Bitcoin Developer Guide. “Transactions.” Accessed November 10, 2026. https://developer.bitcoin.org/devguide/transactions.html.