You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to code, signing PSBT that double spends wallet input in a new transaction that conflicts with another unconfirmed transaction from mempool should work ("utxos that we've stopped tracking"). Probably there is some bug or edge case.
# in the rare situation that we want to sign a psbt using private keys
# to utxos that we've stopped tracking, let's also find inputs that
# belong to us and add those private keys as well
forvininnew_psbt.inputs:
try:
path=self.script_to_path(vin.utxo.scriptPubKey)
key=self._get_key_from_path(path)
ifkeynotinprivkeys:
privkeys.append(key)
exceptAssertionError:
# we can safely assume that an exception means we do not
# have the ability to sign for this input
continue
exceptAttributeError:
# shouldn't happen for properly constructed psbts
# however, psbts with no utxo information will raise
# an AttributeError exception. we simply ignore it.
continue
kristapsk
changed the title
signpsbt do not allow to sign an utxo already spent in an unconfirmed transuction
signpsbt do not allow to sign an utxo already spent in an unconfirmed transaction
Mar 10, 2024
wallet-tool.py signpsbt
do not allow the signing of a transaction spending anutxo
spent in another unconfirmed transaction.The psbt is correctly parsed but
The PSBT is not yet fully signed, we signed: 0 inputs.
is the result of the script.Version 0.9.11
(It is the first issue that I open, so if it is missing any detail let me know)
The text was updated successfully, but these errors were encountered: