Why it exists
BIP 371 gives PSBTs the vocabulary needed for Taproot. A signer needs different information for a Taproot key-path spend and a script-path spend, and the original PSBT fields did not describe all of it. This extension carries that information without putting the private keys into the package.
How it works
Input fields can carry the internal key, Merkle root, leaf scripts and their control blocks, key derivation information, and either a key-path signature or signatures associated with particular script leaves. Output fields can describe a Taproot tree and key origins so a signer can recognize change.
The signer uses the supplied data to reconstruct and check the intended Taproot commitment, then signs the correct BIP 341 message. Finalization builds the witness for the chosen spending path. BIP 371 is an extension to both PSBT v0 and v2; using its fields does not itself require switching to version 2.
A practical example
Consider a wallet with a normal Taproot key path and a delayed recovery leaf. A normal payment needs the information for the key-path signature. A recovery spend instead needs the actual recovery script, its control block and the signatures satisfying that script. Both operations spend the same output, but a coordinator cannot send identical signing instructions for them.
What to keep in mind
“Supports PSBT” does not mean “supports every Taproot policy.” A signer may support simple key-path spending but reject an unfamiliar script tree. Disclosing unnecessary leaves or key origins can also reveal private wallet structure, even before a transaction reaches the chain.
Status & implementation
Bitcoin Core implements BIP 371 fields from 24.0. Taproot consensus activation and support for these application exchange fields are separate milestones.
Specification status: Deployed · Sources checked 13 November 2026
