Skip to main content

bumpfee

Overview

The 'bumpfee' Bumps the fee of an opt-in-RBF transaction T, replacing it with a new transaction B.

Request

wget --no-check-certificate --quiet \
--method POST \
--timeout=0 \
--header 'Content-Type: application/json' \
--header 'accept: application/json' \
--header 'X-CoinAPI-Key: 4303fb63-adec-42dc-b571-74bc2f2a5167' \
--body-data '{"jsonrpc":"2.0","id":1,"method":"bumpfee","params": [ ]}' \
'https://bitcoin-mainnet.node.coinapi.io'

Request Parameters

  • txid: The txid to be bumped
  • options

Response

{
"result": null,
"error": {
"code": -1,
"message": "bumpfee \"txid\" ( options )\n\nBumps the fee of an opt-in-RBF transaction T, replacing it with a new transaction B.\nAn opt-in RBF transaction with the given txid must be in the wallet.\nThe command will pay the additional fee by reducing change outputs or adding inputs when necessary.\nIt may add a new change output if one does not already exist.\nAll inputs in the original transaction will be included in the replacement transaction.\nThe command will fail if the wallet or mempool contains a transaction that spends one of T's outputs.\nBy default, the new fee will be calculated automatically using the estimatesmartfee RPC.\nThe user can specify a confirmation target for estimatesmartfee.\nAlternatively, the user can specify a fee rate in sat/vB for the new transaction.\nAt a minimum, the new fee rate must be high enough to pay an additional new relay fee (incrementalfee\nreturned by getnetworkinfo) to enter the node's mempool.\n* WARNING: before version 0.21, fee_rate was in BTC/kvB. As of 0.21, fee_rate is in sat/vB. *\n\nArguments:\n1. txid (string, required) The txid to be bumped\n2. options (json object, optional)\n {\n \"conf_target\": n, (numeric, optional, default=wallet -txconfirmtarget) Confirmation target in blocks\n \n \"fee_rate\": amount, (numeric or string, optional, default=not set, fall back to wallet fee estimation) \n Specify a fee rate in sat/vB instead of relying on the built-in fee estimator.\n Must be at least 1.000 sat/vB higher than the current transaction fee rate.\n WARNING: before version 0.21, fee_rate was in BTC/kvB. As of 0.21, fee_rate is in sat/vB.\n \n \"replaceable\": bool, (boolean, optional, default=true) Whether the new transaction should still be\n marked bip-125 replaceable. If true, the sequence numbers in the transaction will\n be left unchanged from the original. If false, any input sequence numbers in the\n original transaction that were less than 0xfffffffe will be increased to 0xfffffffe\n so the new transaction will not be explicitly bip-125 replaceable (though it may\n still be replaceable in practice, for example if it has unconfirmed ancestors which\n are replaceable).\n \n \"estimate_mode\": \"str\", (string, optional, default=\"unset\") The fee estimate mode, must be one of (case insensitive):\n \"unset\"\n \"economical\"\n \"conservative\"\n }\n\nResult:\n{ (json object)\n \"txid\" : \"hex\", (string) The id of the new transaction.\n \"origfee\" : n, (numeric) The fee of the replaced transaction.\n \"fee\" : n, (numeric) The fee of the new transaction.\n \"errors\" : [ (json array) Errors encountered during processing (may be empty).\n \"str\", (string)\n ...\n ]\n}\n\nExamples:\n\nBump the fee, get the new transaction's txid\n> bitcoin-cli bumpfee <txid>\n"
},
"id": 1
}