A proposed way to supply a preimage to a wallet
In its Oct. 23, 2026 newsletter, Bitcoin Optech reported that João Dias had proposed extending BIP379 with a private form for hash fragments in miniscript. The proposal addresses a wallet workflow gap: Bitcoin Optech said Bitcoin Core’s wallet could not then be given a preimage directly to satisfy a spending condition.
According to Bitcoin Optech, users currently provide the preimage through external tools in a PSBT hash field. Dias’s proposal would let a user include a preimage in descriptor syntax, so the wallet could use it when constructing and signing a transaction. It is a proposal, not a reported implementation.
Why the preimage matters
A hash fragment is associated with a condition that can be satisfied by supplying its preimage. In the workflow described by Bitcoin Optech, having that value available to the wallet would let it handle the condition while building and signing the transaction, rather than requiring the user to pass it through external tools.
The proposal has a defined boundary
Dias’s proposal covers preimages already known when a descriptor is created, Bitcoin Optech reported. It does not cover preimages learned only at spend time, such as in a hash time-locked contract (HTLC). That distinction limits the proposal to secrets a user can supply in advance; it does not describe a general solution for every spending condition that needs a preimage.