Options for a software signer
Adjust the behavior of our software signers and the way a transaction is finalized
Whether the signer should trust the
witness_utxo, if the
non_witness_utxo hasn’t been
false to mitigate the “SegWit bug” which chould trick the wallet into
paying a fee larger than expected.
Some wallets, especially if relatively old, might not provide the
SegWit transactions in the PSBT they generate: in those cases setting this to
should correctly produce a signature, at the expense of an increased trust in the creator
of the PSBT.
Whether the wallet should assume a specific height has been reached when trying to finalize a transaction
The wallet will only “use” a timelock to satisfy the spending policy of an input if the timelock height has already been reached. This option allows overriding the “current height” to let the wallet use timelocks in the future to spend a coin.
Whether the signer should use the
sighash_type set in the PSBT when signing, no matter
what its value is
false which will only allow signing using
Whether to remove partial signatures from the PSBT inputs while finalizing PSBT.
true which will remove partial signatures during finalization.
Whether to try finalizing the PSBT after the inputs are signed.
true which will try finalizing PSBT after inputs are signed.
Specifies which Taproot script-spend leaves we should sign for. This option is ignored if we’re signing a non-taproot PSBT.
Defaults to All, i.e., the wallet will sign all the leaves it has a key for.
Whether we should try to sign a taproot transaction with the taproot internal key or not. This option is ignored if we’re signing a non-taproot PSBT.
true, i.e., we always try to sign with the taproot internal key.
Whether we should grind ECDSA signature to ensure signing with low r
true, i.e., we always grind ECDSA signature to sign with low r.
Auto Trait Implementations§
Returns the argument unchanged.