Definition: Pay-to-Anchor (P2A) is a Bitcoin output script type designed to leave a compact, keyless output that can be spent as a fee-bumping hook. A wallet can create a child transaction that spends the anchor and pays a higher fee for a package that includes its unconfirmed parent. Bitcoin Core treats P2A spending as standard policy from version 28.0; this does not make P2A a new consensus rule or guarantee relay or confirmation.12
| Specification | Read BIP 433 · Status: Draft |
|---|---|
| Bitcoin Core policy | Spending P2A outputs is standard as of Bitcoin Core v28.0; consensus meaning is unchanged. |
| Directories | Bitcoin Technology & Infrastructure |
How an anchor helps with fees
A Bitcoin transaction pays its own fee, but a transaction signed in advance may not be easy to replace when network fees rise. An anchor output leaves a small output that a later child transaction can spend. The child contributes fees, and nodes that evaluate the parent and child together can assess their combined fee rate. This is the Child Pays for Parent (CPFP) approach. It is useful in protocols that prepare transactions before the fee environment is known, including Lightning commitment transactions and other presigned constructions.1
What makes P2A different
BIP 433 defines the P2A output script as OP_1 <0x4e73>. Its distinctive property is that a standard spend needs no signature or witness data. This makes the anchor keyless: a participant or service able to construct a valid child transaction can attach the fee bump without needing a special anchor key. The BIP describes the corresponding mainnet address as bc1pfeessrawgf. This short output and witness-free spend can reduce overhead in applications where the parties care that someone can raise the package fee, rather than which particular party does it.1
Keyless does not mean harmless or suitable for storing funds. Because no signature is required to spend the anchor, another party can create a competing spend. The anchor should be treated as a narrowly scoped fee-bumping mechanism, not as a normal payment output or a way to protect value with a private key. Application designers must consider transaction pinning and the relay rules of nodes and miners they rely on.
Relay policy is not consensus
BIP 433 is an informational draft in the BIP repository. Bitcoin Core’s implementation makes spending P2A outputs standard under that software’s policy; it does not alter the consensus rules that every validating node uses to decide which blocks are valid. A transaction can be consensus-valid yet fail a node’s local relay policy, and compatible wallet, node, and miner behavior still matters. Bitcoin Core’s BIP implementation index records standard P2A spending from v28.0, while the BIP states that consensus meaning is unchanged.23
Relationship to TRUC and package relay
P2A, Topologically Restricted Until Confirmation (TRUC), and package relay address connected but different parts of fee management. P2A supplies an output that can be spent without a key. TRUC (BIP 431) limits the shape and size of certain unconfirmed transaction chains to make fee bumping less vulnerable to pinning. Package relay concerns how peers communicate and evaluate related unconfirmed transactions. BIP 433 recommends considering TRUC anti-pinning measures when using P2A, but P2A does not itself require TRUC, and neither feature guarantees that a fee bump will propagate everywhere.14
History
- June 2024: Bitcoin Core pull request #30352 proposed standard relay of P2A spends; Bitcoin Core later documented support in v28.0.24
- December 8, 2025: BIP 433 was assigned and published as an informational draft describing the Pay-to-Anchor output type and its standard spend policy.1
Last updated: November 13, 2026.
Criticisms
- Any party can spend a P2A output without a signature. That is useful for shared fee bumping, but it can also let another party interfere with the intended child transaction.
- Wallets, nodes, and miners may apply different relay and package policies. A P2A child can therefore be valid without being relayed or mined as expected.
- P2A is an implementation and policy feature, not a consensus upgrade; support for the output type alone does not make an application’s fee-bumping design robust.
- Applications must account for pinning and fee-market conditions. TRUC and package policies can help in some designs but do not remove every operational or incentive risk.
Related Terms
- Child Pays for Parent (CPFP)
- Lightning Network
- Bitcoin Transaction Fees
- Topologically Restricted Until Confirmation (TRUC)
Related Articles
- What Happens to Bitcoin When All 21 Million Are Mined?
- Are Layer 2 Networks Actually Decentralized?
- Why Smart Contract Audits Fail
- How Do Crypto Bridges Work—and Why Are They Such a Hack Target?
See Also
Sources
- Sanders, Gregory. “BIP 433: Pay to Anchor (P2A).” Bitcoin Improvement Proposals. Assigned December 8, 2025. Accessed November 13, 2026. https://github.com/bitcoin/bips/blob/master/bip-0433.mediawiki.
- 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.
- Bitcoin Core. “BIPs Implemented by Bitcoin Core.” Bitcoin Core Documentation. Accessed November 13, 2026. https://github.com/bitcoin/bitcoin/blob/master/doc/bips.md.
- Bitcoin Core. “Standardize Pay-to-Anchor (P2A) Outputs for Spending.” Pull request #30352. Accessed November 13, 2026. https://github.com/bitcoin/bitcoin/pull/30352.