Dec 19 - Nov 18, 2026
These innovations enable more versatile spending policies, especially where certain conditions—like timelocks or multi-party thresholds—cannot be efficiently managed through keypaths alone. One central challenge has been the construction and use of unspendable keys, which allow wallets to function exclusively through script paths when necessary. Creating these keys appears simple on the surface, using techniques such as constructing extended public keys (xpubs) from Nothing-Up-My-Sleeve (NUMS) points with a zeroed chaincode. However, achieving practical and secure implementations demands that such keys remain indistinguishable from ordinary keys to external observers, are unique and non-linkable, and can be efficiently identified and utilized within descriptor frameworks—all while minimizing complexity for users interacting with hardware devices.
Multiple methods for generating unspendable keys have been explored. Options include fixed unspendable xpubs, root xpubs with random chaincodes, approaches outlined in BIP-0341, and entropy recycling techniques where entropy is drawn from either the taptree or the descriptor itself. Recycling entropy by hashing all compressed pubkeys in a descriptor and pairing the result with a fixed chaincode offers a promising balance of uniqueness and non-fingerprinting, especially if supported by a clear marker in the descriptor to denote this special xpub. While root xpubs with random chaincodes offer practical compatibility with hardware signers, they introduce minor user experience trade-offs due to the need for additional entropy. Long-term, embedding entropy deterministically within wallet policies could streamline both security and ease of use, though widespread adoption of such policies as a backup standard for descriptors remains under discussion.
At TabConf 2022, an in-depth exchange among developers focused on enhancing miniscript and output descriptors, with particular attention given to the role of unspendable keys. A foundational resource on this topic, Unspendable Keys Gist by Pieter Wuille, was referenced for further exploration and to inform ongoing proposals. The utility of provably unspendable keypaths extends beyond theoretical constructs, finding application in protocols such as BIP352 for silent payments, where a standard NUMS point ("H") is used to guarantee unspendability in a verifiable manner. Standardizing on a public NUMS streamlines cross-platform verification but raises questions regarding privacy and the risk of unwanted transaction fingerprinting, especially in situations where revealing the internal key exposes a transaction as script-only, potentially compromising user anonymity.
Privacy considerations are paramount in discussions about whether to standardize on a publicly known NUMS. If a taproot output is spent only via its script path, disclosing the internal key may immediately reveal the nature of the transaction, making it easier to single out specific transaction types or participants. Such transparency might not always be desirable; it could introduce new vectors for discrimination or censorship, affecting fungibility and participant privacy. For instance, if some organizations consistently use script-only paths, adversaries could target or flag their transactions. Hence, while standardization aids protocol development and interoperability, a nuanced approach is needed, weighing the benefits against potential privacy trade-offs case by case.
Digital fingerprinting serves as a central metaphor throughout the debate. Just as physical fingerprints uniquely identify individuals, complex scripts or provably unspendable keypaths can act as digital signatures within the blockchain, exposing transaction patterns upon every use. Protocols should be designed with voluntary disclosure in mind, empowering users to control what identifying information is revealed and when. This ethos supports a flexible approach to cryptographic standards, avoiding mandatory exposure of a keypath's spendability status except where strictly necessary for contractual proofs among involved parties.
From a technical perspective, issues arise when attempting to create Bitcoin addresses using partial descriptors. Such descriptors require supplemental off-chain information, meaning that address generation is not autonomous nor fully verifiable solely from on-chain data. Developers therefore express preference for architectures in which all necessary entropy is contained within the descriptor itself, reducing dependencies and preserving the decentralized and self-contained nature of Bitcoin’s design. This focus enhances both security and user autonomy, as it eliminates reliance on unverifiable or third-party data sources.
A further distinction emerges between requirements for output descriptors and wallet policies. Output descriptors benefit from explicit definitions of entropy via unspendable key markers like unspend(), ensuring deterministic and clear specification of spend conditions. Wallet policies, conversely, can operate under the assumption that all relevant data—including entropy—is implicitly derived from their deterministic structure, obviating the need for explicit entropy declarations and simplifying policy management without sacrificing security.
The practical implementation of unspendable internal keys is advancing rapidly, particularly within projects like Liana, which aim to optimize user
Thread Summary (34 replies)
Dec 19 - Nov 18, 2026
35 messages
TLDR
We’ll email you summaries of the latest discussions from high signal bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.
We'd love to hear your feedback on this project.
Give Feedback