Add explicit feeRate option for sendmany RPC method #19662

issue yurayakimenko opened this issue on August 4, 2020
  1. yurayakimenko commented at 6:11 PM on August 4, 2020: none

    Is your feature request related to a problem? Please describe. It's always hard to send a bunch of transactions with sendmany method using conf_target option. Cause build-in fee estimator not suggesting required fee rate for our purposes. How could I specify transaction fee in BTC/kB for sendmany without creating raw transaction (building outputs and inputs manually)?

    Describe the solution you'd like Add fee_rate option to sendmany RPC method.

    Describe alternatives you've considered Currently I'm trying to estimate required conf_target based on mempool size and making weird algorithms that limiting that value someway.

    Additional context That is not so convenient for us. So the better solution would be to provide fee_rate option that is much easier to manipulate. Thanks in advance!

  2. yurayakimenko added the label Feature on Aug 4, 2020
  3. MarcoFalke added the label Wallet on Aug 5, 2020
  4. MarcoFalke commented at 7:38 AM on August 5, 2020: member

    This is being worked on, see #19543

  5. yurayakimenko commented at 10:12 AM on August 5, 2020: none

    @MarcoFalke my feature request is not about normalizing units, it's about adding fee_rate option to sendmany RPC method!

  6. MarcoFalke commented at 10:30 AM on August 5, 2020: member

    #11413 has been merged, #19543 is the second step

  7. yurayakimenko commented at 10:33 AM on August 5, 2020: none

    @MarcoFalke #11413 would be in release version only after #19543 would be done?

  8. jonatack commented at 10:40 AM on August 5, 2020: member

    You can use #11413 now in master; I recently used the explicit feerate option on master with sendtoaddress to make a near-instant yet relatively inexpensive payment on a busy mempool day and it worked very well.

  9. jonatack commented at 7:24 PM on December 5, 2020: member

    This feature request has been delivered, e.g. with #11413 and #20305, and ISTM this issue can be closed.

  10. adamjonas closed this on Jan 15, 2021

  11. DrahtBot locked this on Aug 18, 2022

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-21 15:14 UTC

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