Definition: Miniscript is a structured language for expressing and analyzing a subset of Bitcoin Script spending conditions. It lets developers compose requirements such as signatures, hash preimages, timelocks, and thresholds, then reason about how a valid spend can satisfy them. Miniscript does not change Bitcoin’s consensus rules; the resulting script still has to be valid under those rules.14
| Purpose | A structured way to compose and analyze Bitcoin Script spending conditions |
| Specification | BIP 379 (Draft; assigned October 10, 2023)1 |
| Bitcoin Core | Partial Miniscript implementation in v24.0; full implementation as of v26.02 |
| Descriptor contexts | Miniscript expressions are supported inside wsh() and tr() output descriptors3 |
| Directory | Bitcoin Directory |
How Miniscript relates to Bitcoin Script
Bitcoin Script is the stack-based language that evaluates the conditions for spending certain Bitcoin outputs. Writing a complicated spending policy directly in Script can be difficult to review: a developer may need to combine several keys, alternative recovery paths, hashes, or time requirements while checking that the script is valid and economical to spend. Miniscript gives compatible parts of Script a structured representation. A policy can be composed from smaller conditions and translated into a script, while tools can inspect what the script permits and what a signer may need to provide.14
Common policy building blocks
These examples show the kinds of conditions that can be expressed. The exact expression and its meaning depend on the script context and the policy being composed.
| Requirement | Example form | What it expresses |
|---|---|---|
| Signature | pk(A) | A signature from the key represented by A is required. |
| Absolute timelock | after(N) | The transaction must satisfy an absolute locktime requirement. |
| Relative timelock | older(N) | The input must satisfy a relative sequence or age requirement. |
| Hash preimage | sha256(H) | A value whose SHA-256 hash matches H must be provided. |
| Threshold | thresh(K,...) | A specified number of subconditions must be met. |
What analysis adds
The structure gives software a clearer way to reason about a spending condition than an opaque script alone. Depending on the expression and implementation, analysis can help identify its possible spending paths, compose policies, construct satisfying witness data, estimate spend costs, and check for certain correctness or resource-limit problems. These checks help wallet and signing software coordinate complex scripts, but they do not certify that a wallet is secure or that a user’s overall custody setup is safe.14
Descriptors, wallets, and compatibility
Bitcoin Core documents Miniscript expressions within the wsh() descriptor for pay-to-witness-script-hash outputs and the tr() descriptor for Taproot outputs. Descriptors describe output scripts and help wallet software track the outputs that belong to a wallet. That does not mean every wallet, hardware signer, coordinator, or recovery tool supports every Miniscript expression or descriptor form. Before relying on a policy, confirm that each wallet and signer can import it, derive the expected addresses, display the spending conditions, and produce or recover a valid spend. Keep the descriptor and backup instructions available to the people who may need to recover the funds.3
Limits and risks
Miniscript is a representation and analysis framework, not a new Bitcoin consensus feature, a wallet, or a guarantee that a policy is well designed. The supported subset and details differ between script contexts, and individual tools can implement different parts of the language. A policy may also be technically valid yet impractical if signers cannot coordinate, backups omit the descriptor, a timelock is misunderstood, or recovery depends on unavailable keys. Test the intended spend and recovery path with the actual software and signers before placing meaningful funds under a complex script. Do not assume that a successful analysis replaces independent review of the policy or the wallet implementation.134
History
- 2019: An early version of Miniscript was presented at Scaling Bitcoin, as noted by the project’s reference site.4
- 2022: Bitcoin Core v24.0 included a partial implementation of Miniscript.2
- 2023: Bitcoin Core v26.0 completed the implementation described by the project’s BIP status document. BIP 379 was assigned on October 10 and remains labeled Draft in the proposal document.12
Page updated: November 10, 2026.
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
- Bitcoin and the Stock Market: What Correlation Can—and Can’t—Tell You
See Also
Sources
- Bitcoin Improvement Proposals. “BIP 379: Miniscript.” Assigned October 10, 2023. Status: Draft. Accessed November 10, 2026. BIP 379.
- Bitcoin Core Developers. “BIPs Implemented by Bitcoin Core.” Accessed November 10, 2026. Bitcoin Core BIP implementation notes.
- Bitcoin Core Developers. “Output Script Descriptors.” Accessed November 10, 2026. Bitcoin Core descriptor documentation.
- Wuille, Pieter, Andrew Poelstra, and Sanket Kanjalkar. “Miniscript.” Accessed November 10, 2026. Miniscript reference and compiler.