wallet: rpc: manpage: fix example missing `fee_rate` argument #34561

pull SomberNight wants to merge 1 commits into bitcoin:master from SomberNight:202602_fix_manpage_send_rpc changing 1 files +1 −1
  1. SomberNight commented at 4:24 PM on February 11, 2026: contributor

    The function signature for the send RPC is:

    send [{"address":amount,...},{"data":"hex"},...] ( conf_target "estimate_mode" fee_rate options version )
    

    The last example in the manpage is missing the fee_rate arg, but is trying to specify the options arg, by index. The parser confuses the intended options arg as the missing fee_rate arg.

    See:

    $ bitcoin-cli -rpcuser=doggman -rpcpassword=donkey -rpcport=18554 -regtest send '{"bcrt1qusm48zmlzwr32csxdw4ar7atw260h22c9ten9l": 0.1}' 1 economical '{"add_to_wallet": false, "inputs": [{"txid":"0b7e1a471dc948b7a6187936b16e6d7d9833629b2f9dd8a392eb89928f63aaad", "vout":0}]}'
    error code: -8
    error message:
    Cannot specify both conf_target and fee_rate. Please provide either a confirmation target in blocks for automatic fee estimation, or an explicit fee rate.
    

    vs

    $ bitcoin-cli -rpcuser=doggman -rpcpassword=donkey -rpcport=18554 -regtest send '{"bcrt1qusm48zmlzwr32csxdw4ar7atw260h22c9ten9l": 0.1}' 1 economical null '{"add_to_wallet": false, "inputs": [{"txid":"0b7e1a471dc948b7a6187936b16e6d7d9833629b2f9dd8a392eb89928f63aaad", "vout":0}]}'
    {
      "psbt": "cHNidP8BAHECAAAAAa2qY4+SieuSo9idL5tiM5h9bW6xNnkYprdIyR1HGn4LAAAAAAD9////AkR2DwQAAAAAFgAUpLDwJu+wFRHLQAgKAb0psk7UVd2AlpgAAAAAABYAFOQ3U4t/E4cVYgZrq9H7q3K0+6lYAAAAAAABAIUCAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/////wQC4wMA/////wLIF6gEAAAAABYAFLMY1zihXrefAA0DA5nld4MCPjkrAAAAAAAAAAAmaiSqIant4vYcP3HR3v0/qZnfo2lTdVxpBol5mWK0i+vYNpdOjPkAAAAAAQEfyBeoBAAAAAAWABSzGNc4oV63nwANAwOZ5XeDAj45KwEIawJHMEQCIElTV4pbUrsPR9qHWcioowVv3QVWHizxwevfD0u/I8YyAiBCY3OzF81PSLM00h4ueQkehYuxDFZu7Jk51iejphKnnwEhA0VKdYVSyBpWoxBwTDOupB58Fi3mEBs+u+OOqEYVd2sZACICA98YLWyH7dBCfXVxe7woiLSTgV1mJN8Zc8KgZ77pVSg+GNBMeT5UAACAAQAAgAAAAIABAAAAbAAAAAAA",
      "txid": "625b71b314a6ac4f738634e29dc007cd5edc0427c1ae96ab706d06a62910cea2",
      "hex": "02000000000101adaa638f9289eb92a3d89d2f9b6233987d6d6eb1367918a6b748c91d471a7e0b0000000000fdffffff0244760f0400000000160014a4b0f026efb01511cb40080a01bd29b24ed455dd8096980000000000160014e437538b7f13871562066babd1fbab72b4fba9580247304402204953578a5b52bb0f47da8759c8a8a3056fdd05561e2cf1c1ebdf0f4bbf23c6320220426373b317cd4f48b334d21e2e79091e858bb10c566eec9939d627a3a612a79f012103454a758552c81a56a310704c33aea41e7c162de6101b3ebbe38ea84615776b1900000000",
      "complete": true
    }
    
  2. wallet: rpc: manpage: fix example missing `fee_rate` argument
    The function signature for the `send` RPC is:
    ```
    send [{"address":amount,...},{"data":"hex"},...] ( conf_target "estimate_mode" fee_rate options version )
    ```
    
    The last example in the manpage is missing the `fee_rate` arg, but is trying to specify the `options` arg, by index.
    The parser confuses the intended `options` arg as the missing `fee_rate` arg.
    
    See:
    ```
    $ bitcoin-cli -rpcuser=doggman -rpcpassword=donkey -rpcport=18554 -regtest send '{"bcrt1qusm48zmlzwr32csxdw4ar7atw260h22c9ten9l": 0.1}' 1 economical '{"add_to_wallet": false, "inputs": [{"txid":"0b7e1a471dc948b7a6187936b16e6d7d9833629b2f9dd8a392eb89928f63aaad", "vout":0}]}'
    error code: -8
    error message:
    Cannot specify both conf_target and fee_rate. Please provide either a confirmation target in blocks for automatic fee estimation, or an explicit fee rate.
    ```
    vs
    ```
    $ bitcoin-cli -rpcuser=doggman -rpcpassword=donkey -rpcport=18554 -regtest send '{"bcrt1qusm48zmlzwr32csxdw4ar7atw260h22c9ten9l": 0.1}' 1 economical null '{"add_to_wallet": false, "inputs": [{"txid":"0b7e1a471dc948b7a6187936b16e6d7d9833629b2f9dd8a392eb89928f63aaad", "vout":0}]}'
    {
      "psbt": "cHNidP8BAHECAAAAAa2qY4+SieuSo9idL5tiM5h9bW6xNnkYprdIyR1HGn4LAAAAAAD9////AkR2DwQAAAAAFgAUpLDwJu+wFRHLQAgKAb0psk7UVd2AlpgAAAAAABYAFOQ3U4t/E4cVYgZrq9H7q3K0+6lYAAAAAAABAIUCAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/////wQC4wMA/////wLIF6gEAAAAABYAFLMY1zihXrefAA0DA5nld4MCPjkrAAAAAAAAAAAmaiSqIant4vYcP3HR3v0/qZnfo2lTdVxpBol5mWK0i+vYNpdOjPkAAAAAAQEfyBeoBAAAAAAWABSzGNc4oV63nwANAwOZ5XeDAj45KwEIawJHMEQCIElTV4pbUrsPR9qHWcioowVv3QVWHizxwevfD0u/I8YyAiBCY3OzF81PSLM00h4ueQkehYuxDFZu7Jk51iejphKnnwEhA0VKdYVSyBpWoxBwTDOupB58Fi3mEBs+u+OOqEYVd2sZACICA98YLWyH7dBCfXVxe7woiLSTgV1mJN8Zc8KgZ77pVSg+GNBMeT5UAACAAQAAgAAAAIABAAAAbAAAAAAA",
      "txid": "625b71b314a6ac4f738634e29dc007cd5edc0427c1ae96ab706d06a62910cea2",
      "hex": "02000000000101adaa638f9289eb92a3d89d2f9b6233987d6d6eb1367918a6b748c91d471a7e0b0000000000fdffffff0244760f0400000000160014a4b0f026efb01511cb40080a01bd29b24ed455dd8096980000000000160014e437538b7f13871562066babd1fbab72b4fba9580247304402204953578a5b52bb0f47da8759c8a8a3056fdd05561e2cf1c1ebdf0f4bbf23c6320220426373b317cd4f48b334d21e2e79091e858bb10c566eec9939d627a3a612a79f012103454a758552c81a56a310704c33aea41e7c162de6101b3ebbe38ea84615776b1900000000",
      "complete": true
    }
    ```
    50cf6838e6
  3. DrahtBot added the label Wallet on Feb 11, 2026
  4. DrahtBot commented at 4:24 PM on February 11, 2026: contributor

    <!--e57a25ab6845829454e8d69fc972939a-->

    The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

    <!--021abf342d371248e50ceaed478a90ca-->

    Reviews

    See the guideline for information on the review process.

    Type Reviewers
    ACK rkrux, svanstaa, theStack, kannapoix, achow101

    If your review is incorrectly listed, please copy-paste <code>&lt;!--meta-tag:bot-skip--&gt;</code> into the comment that the bot should ignore.

    <!--5faf32d7da4f0f540f40219e4f7537a3-->

  5. rkrux approved
  6. rkrux commented at 2:37 PM on February 12, 2026: contributor

    tACK 50cf6838e6aa51e0d712cbc1e13d686253bc8fe0

  7. svanstaa commented at 3:25 PM on February 12, 2026: none

    tACK https://github.com/bitcoin/bitcoin/commit/50cf6838e6aa51e0d712cbc1e13d686253bc8fe0

    I have replicated the described behaviour in v.30.2

    $ bitcoin-cli -regtest help send
    send [{"address":amount,...},{"data":"hex"},...] ( conf_target "estimate_mode" fee_rate options version )
    
    [...]
    
    Examples:
    
    [...]
    
    Create a transaction that should confirm the next block, with a specific input, and return result without adding to wallet or broadcasting to the network
    bitcoin-cli send '{"bc1q09vm5lfy0j5reeulh4x5752q25uqqvz34hufdl": 0.1}' 1 economical '{"add_to_wallet": false, "inputs": [{"txid":"a08e6907dbbd3d809776dbfc5d82e371b764ed838b5655e72f463568df1aadf0", "vout":1}]}'
    

    Using the exact syntax from the last manpage example fails:

    $ bitcoin-cli -regtest send '{"bcrt1qusm48zmlzwr32csxdw4ar7atw260h22c9ten9l": 0.1}' 1 economical '{"add_to_wallet": false, "inputs": [{"txid":"f44f60ac9663cd32cdff9461dfe1446bb8ed2fd4b0d77a35683af685bb320b29", 
    "vout":0}]}'
    error code: -8
    error message:
    Cannot specify both conf_target and fee_rate. Please provide either a confirmation target in blocks for automatic fee estimation, or an explicit fee rate.
    

    Works with adding 'null' as a placeholder for the fee_rate argument:

    $ bitcoin-cli -regtest send '{"bcrt1qusm48zmlzwr32csxdw4ar7atw260h22c9ten9l": 0.1}' 1 economical null '{"add_to_wallet": false, "inputs": [{"txid":"f44f60ac9663cd32cdff9461dfe1446bb8ed2fd4b0d77a35683af685bb320b
    29", "vout":0}]}'
    {
      "psbt": "cHNidP8BAHECAAAAASkLMruF9jpoNXrXsNQv7bhrROHfYZT/zTLNY5asYE/0AAAAAAD9////AoCWmAAAAAAAFgAU5DdTi38ThxViBmur0furcrT7qVjzWm0pAQAAABYAFLzgDy3hiwk5C8E+O4JHJ078S+TSZQAAAAABAIMCAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/////wJRAP7///8CAPIFKgEAAAAWABTv42ILrPHD22DH/eGOm+tGQvZzkQAAAAAAAAAAJmokqiGp7eL2HD9x0d79P6mZ36NpU3VcaQaJeZlitIvr2DaXToz5AAAAAAEBHwDyBSoBAAAAFgAU7+NiC6zxw9tgx/3hjpvrRkL2c5EBCGsCRzBEAiBq8k/dDzOKtUSYP3NvOq5rVG5UTcCyxoy9xIjqql1kegIgALvsEG+a3+bStSrRX83UI00vzkLp3mTmIVXw9qDzGCgBIQJ8oHJIVCbQxRiO+JtLVqrHDLJAxlG4IeF0gpiHMFZp9wAAIgIDCZ9ZADFv4D37y0nqeX8PTn2+ifDnUlEw60GoWWnWbo0YAu398FQAAIABAACAAAAAgAEAAAABAAAAAA==",
      "txid": "cab9cdb204bbfadc44d1a0867e904cb9463b4844cbb6438b56c49d47fa9da870",
      "hex": "02000000000101290b32bb85f63a68357ad7b0d42fedb86b44e1df6194ffcd32cd6396ac604ff40000000000fdffffff028096980000000000160014e437538b7f13871562066babd1fbab72b4fba958f35a6d2901000000160014bce00f2de18b09390bc13e3b8247274efc4be4d20247304402206af24fdd0f338ab544983f736f3aae6b546e544dc0b2c68cbdc488eaaa5d647a022000bbec106f9adfe6d2b52ad15fcdd4234d2fce42e9de64e62155f0f6a0f318280121027ca072485426d0c5188ef89b4b56aac70cb240c651b821e174829887305669f765000000",
      "complete": true
    }
    
  8. theStack approved
  9. theStack commented at 6:20 PM on February 23, 2026: contributor

    Tested ACK 50cf6838e6aa51e0d712cbc1e13d686253bc8fe0

    Also verified on regtest that the other send examples are working (with a proper bcrt1... address).

  10. kannapoix commented at 2:36 AM on February 24, 2026: none

    Tested ACK 50cf6838e6aa51e0d712cbc1e13d686253bc8fe0

  11. achow101 commented at 10:15 PM on February 24, 2026: member

    ACK 50cf6838e6aa51e0d712cbc1e13d686253bc8fe0

  12. achow101 merged this on Feb 24, 2026
  13. achow101 closed this on Feb 24, 2026

  14. fanquake commented at 10:06 AM on February 25, 2026: member

    Backported to 30.x in #34459.

  15. fanquake referenced this in commit d54d7dfe9f on Feb 25, 2026
  16. fanquake referenced this in commit 98af76f875 on Feb 26, 2026
  17. fanquake commented at 10:12 AM on February 26, 2026: member

    Backported to 29.x in #34680.


github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-13 15:12 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me