Why it exists
BIP 386 defines tr(), the descriptor expression for Taproot outputs. It can describe an internal key alone or an internal key combined with a script tree. This records the information needed to reconstruct the output commitment and its alternative spending paths.
How it works
tr(KEY) constructs a key-path-only wallet output using the Taproot tweak. tr(KEY,TREE) additionally commits to a tree of scripts. The tree uses nested pairs to describe how script branches are arranged.
The internal key and the tree root determine the tweaked output key. A script-path spend reveals its chosen script and proof, not every possible branch. Therefore the original tree structure matters: the same leaves arranged differently can commit to a different output.
A practical example
A wallet might offer a normal key-path spend plus an alternative script path. Its recovery record must preserve the internal-key expression, the fallback script and the tree arrangement. Keeping only the fallback private key does not by itself reproduce the Taproot output or its proof.
What to keep in mind
The tr() expression does not guarantee that a device understands every script fragment inside it. Public descriptors also disclose policy information. A backup of an ordinary BIP 86 single-key account is a simpler case than a custom Taproot tree and should not be assumed to recover one.
Status & implementation
The BIP is Deployed. Core documents tr() support from 22.0. Its current descriptor documentation separately lists supported Taproot script expressions, so parsing the outer tr() wrapper is only one part of policy compatibility.
Specification status: Deployed · Sources checked 13 November 2026
