Bitcoin · CryptoSlate
Bitcoin Core’s new address closes gap that could redirect funds without stealing keys
Compiled by KHAO Editorial — aggregated from 1 source. See llms.txt for citation guidance.
◌ Single Source
Bitcoin Core has added a safeguard against signing transactions that may not bind funds to the payment destination a user approved.
Key facts
- Bitcoin Improvement Proposal 174, which defines PSBTs, already tells signers to reject unacceptable signing modes and recommends SIGHASH_ALL when no alternative is specified
- The change, merged into Bitcoin Core’s master development branch on Sept
- Bitcoin Core has added a safeguard against signing transactions that may not bind funds to the payment destination a user approved
- Bitcoin Core already rejected the edge case through its raw-transaction signing interface
Summary
01 Bitcoin Core added a safeguard against PSBT signatures that may not bind funds to the destination a user approved. 02 The flaw could let a valid signature survive recipient changes without exposing the owner’s private key. The fix is only in Bitcoin Core’s development branch, leaving wallet providers to review their own signing logic now. The change, merged into Bitcoin Core’s master development branch on Sept. 25, targets a narrow flaw in partially signed Bitcoin transactions, or PSBTs, that could produce a valid signature without protecting the intended output.