psbtbumpfee
Wallet
Summary
Bumps the fee of a transaction T, replacing it with a new transaction B.
Description
Bumps the fee of a transaction T, replacing it with a new transaction B. Returns a PSBT instead of creating and signing a new transaction. A transaction with the given txid must be in the wallet. The command will pay the additional fee by reducing change outputs or adding inputs when necessary. It may add a new change output if one does not already exist. All inputs in the original transaction will be included in the replacement transaction. The command will fail if the wallet or mempool contains a transaction that spends one of T's outputs. By default, the new fee will be calculated automatically using the estimatesmartfee RPC. The user can specify a confirmation target for estimatesmartfee. Alternatively, the user can specify a fee rate in sat/vB for the new transaction. At a minimum, the new fee rate must be high enough to pay an additional new relay fee (incrementalfee returned by getnetworkinfo) to enter the node's mempool. * WARNING: before version 0.21, fee_rate was in QBT/kvB. As of 0.21, fee_rate is in sat/vB. *
Arguments
txid(STR_HEX, required): The txid to be bumpedoptions(OBJ_NAMED_PARAMS): No description.-
conf_target(NUM): Confirmation target in blocks -
fee_rate(AMOUNT): Specify a fee rate in sat/vB instead of relying on the built-in fee estimator. Must be at least 0.250 sat/vB higher than the current transaction fee rate. WARNING: before version 0.21, fee_rate was in QBT/kvB. As of 0.21, fee_rate is in sat/vB. -
replaceable(BOOL): Whether the new transaction should be marked bip-125 replaceable. If true, the sequence numbers in the transaction will be set to 0xfffffffd. If false, any input sequence numbers in the transaction will be set to 0xfffffffe so the new transaction will not be explicitly bip-125 replaceable (though it may still be replaceable in practice, for example if it has unconfirmed ancestors which are replaceable). -
estimate_mode(STR): The fee estimate mode, must be one of (case insensitive): unset, economical, conservative unset means no mode set (economical mode is used if the transaction is replaceable; otherwise, conservative mode is used). economical estimates use a shorter time horizon, making them more responsive to short-term drops in the prevailing fee market. This mode potentially returns a lower fee rate estimate. conservative estimates use a longer time horizon, making them less responsive to short-term drops in the prevailing fee market. This mode potentially returns a higher fee rate estimate. -
outputs(ARR): The outputs specified as key-value pairs. Each key may only appear once, i.e. there can only be one 'data' output, and no address may be duplicated. At least one output of either type must be specified. Cannot be provided if 'original_change_index' is specified.value(OBJ_USER_KEYS): No description.address(AMOUNT, required): A key-value pair. The key (string) is the qbit address, the value (float or string) is the amount in QBTvalue(OBJ): No description.data(STR_HEX, required): A key-value pair. The key must be "data", the value is hex-encoded data that becomes a part of an OP_RETURN output
original_change_index(NUM): The 0-based index of the change output on the original transaction. The indicated output will be recycled into the new change output on the bumped transaction. The remainder after paying the recipients and fees will be sent to the output script of the original change output. The change output’s amount can increase if bumping the transaction adds new inputs, otherwise it will decrease. Cannot be used in combination with the 'outputs' option.
Results
value(OBJ): No description.psbt(STR): The base64-encoded unsigned PSBT of the new transaction.origfee(STR_AMOUNT): The fee of the replaced transaction.fee(STR_AMOUNT): The fee of the new transaction.errors(ARR): Errors encountered during processing (may be empty).value(STR): No description.
Examples
Bump the fee, get the new transaction's psbt
qbit-cli psbtbumpfee <txid>