Why it exists
BIP 379 specifies Miniscript, a structured way to express a subset of Bitcoin Script. It makes conditions such as signatures and time locks easier for software to compose, analyse and satisfy. It does not introduce a new consensus language or make arbitrary scripts understandable.
How it works
Miniscript uses fragments with defined properties and composition rules. A tool can determine which signatures or other data are required, estimate satisfaction costs and reason about resource limits. The fragments translate into existing script operations rather than asking nodes to execute Miniscript text.
The specification covers P2WSH and Tapscript contexts, with relevant differences between them. Miniscript expressions sit inside wsh() or tr() descriptors, which also carry the wallet’s keys and output structure. The complete descriptor remains important for recovery and for reproducing the intended policy.
A practical example
A policy might require both Alice and Bob for normal spending, with a separate recovery key allowed after a delay. Compatible tooling can analyse those alternative paths and construct a witness for an available path. Whether a delay counts from a particular confirmation or a fixed date depends on the chosen timelock.
What to keep in mind
Analysable does not mean suitable for every user. Key custody, fee funding, backup completeness and signer support still determine whether recovery works. A policy can be technically valid while contradicting the owner’s intent, so a small end-to-end rehearsal remains essential.
Status & implementation
BIP 379 is Draft, while implementations already exist. Bitcoin Core 31.0’s descriptor documentation explicitly supports Miniscript within wsh() and tr(). Document status and availability in particular software therefore need to be read separately.
Specification status: Draft · Sources checked 13 November 2026
