allow RPC send commands to specify TX fee per TX #210

issue mikegogulski opened this issue on May 9, 2011
  1. mikegogulski commented at 3:22 PM on May 9, 2011: none

    bitcoin@btcserver:~/bitcoin-0.3.21/bin/32$ ./bitcoind sendtoaddress 16bRQcbr1xxxu27ZQxqGhi242eL 0.2 error: {"code":-4,"message":"Error: This transaction requires a transaction fee of at least 0.01 because of its amount, complexity, or use of recently received funds "}

    I guess in the first place I'd like an error message which comes back with a "TXFEEREQUIRED" status, giving that fee as its value, rather than needing to parse English text to find it.

    In the second place, I'd like to be able to do something like:

    try {
      rpc_bitcoind("sendtoaddress", address, amount);
    } catch (bitcoindexception e) {
      if (e->txfee) {
        try {
          rpc_bitcoind("sendtoaddress", address, amount, e->txfee);
        } catch {
          debug("zomgwtflolbbq");
        }
      } else {
        debug("fail", e.toString());
      }
    }
    
  2. Plasma commented at 7:03 AM on August 15, 2011: none

    Agreed, this would be fantastic.

  3. jgarzik commented at 9:26 PM on July 5, 2012: contributor

    $Subject appears to differ from $IssueText.

    You may now specify TX fees on per-TX basis via the raw TX RPC API (solves $subject).

    However, as $IssueText notes, the error returned from an insufficient fee is difficult to parse, so I must leave this issue open.

  4. laanwj added the label Wallet on Sep 25, 2014
  5. sipa referenced this in commit 0350c7e4b8 on Jul 28, 2015
  6. sipa referenced this in commit 7863d105ea on Aug 4, 2015
  7. sipa referenced this in commit 780d5b3c7b on Aug 23, 2015
  8. dexX7 referenced this in commit a9eb96067c on Aug 31, 2015
  9. paveljanik commented at 11:08 AM on October 1, 2015: contributor

    Duplicate of #211

  10. laanwj commented at 12:29 PM on October 1, 2015: member

    Right, #211 reports the same issue. This is confusing.

  11. laanwj closed this on Oct 1, 2015

  12. TheBlueMatt referenced this in commit 582b2934e6 on Oct 20, 2015
  13. TheBlueMatt referenced this in commit a671356e1f on Oct 20, 2015
  14. sipa referenced this in commit 9177950c74 on Oct 21, 2015
  15. sipa referenced this in commit f4787d1caf on Oct 21, 2015
  16. sipa referenced this in commit 6557a8cd46 on Oct 26, 2015
  17. sipa referenced this in commit ea06490d14 on Oct 27, 2015
  18. sipa referenced this in commit 003bb87153 on Nov 5, 2015
  19. sipa referenced this in commit bfd83199c3 on Nov 11, 2015
  20. sipa referenced this in commit b437ea7ec9 on Nov 12, 2015
  21. sipa referenced this in commit 1d84107924 on Nov 12, 2015
  22. btcdrak referenced this in commit cae9e5cd50 on Nov 28, 2015
  23. rebroad referenced this in commit 40ead34fbe on Dec 7, 2016
  24. deadalnix referenced this in commit 6982887f0b on Jan 6, 2017
  25. deadalnix referenced this in commit 729badff14 on Jan 19, 2017
  26. lateminer referenced this in commit 798cc5bd2c on Dec 9, 2017
  27. classesjack referenced this in commit 2ebdbb9ebf on Jan 2, 2018
  28. nining referenced this in commit 0206fe3a1a on Jan 3, 2018
  29. attilaaf referenced this in commit 6618d1b065 on Jan 13, 2020
  30. Losangelosgenetics referenced this in commit afb9f6bb79 on Mar 12, 2020
  31. rajarshimaitra referenced this in commit 4d24b1c404 on Aug 5, 2021
  32. DrahtBot locked this on Sep 8, 2021

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 21:16 UTC

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