Better Fee UI #289

pull TheBlueMatt wants to merge 3 commits into bitcoin:master from TheBlueMatt:feefix changing 11 files +1313 −679
  1. TheBlueMatt commented at 10:17 PM on June 1, 2011: member

    In 3 commits: Make the fee error/dialog messages much clearer.

    Update fee policy to be much more customizable. This changes nTransactionFee into nBaseTransactionFee and nPerKBTransactionFee where nBaseTransactionFee is applied to each transaction once and nPerKBTransactionFee is applied per KB to each transaction. Also, fOverrideTransactionFee has been added to allow the ignoring of GetMinFee() when creating transactions.

    Add setautocommit, reject transaction and committransaction. Here is the help for setautocommit: If <autocommit> is false, the send* functions will return a txid, which must be manually committed instead of being immediately committed. Once a new transaction has been created, you can get information about it by using gettransaction <txid>. It can then be commited or rejected using committransaction <txid> or rejecttransaction <txid> respectively.

    Forum thread at http://forum.bitcoin.org/index.php?topic=10923.0

  2. gavinandresen commented at 6:31 PM on June 4, 2011: contributor

    I assume The Right Thing happens if I:

    setautocommit false send.... stop

    (the Right Thing being that when I restart the txid from the send is just completely unknown and the coins that were in committed state when bitcoin stopped are available to be sent?)

  3. TheBlueMatt commented at 10:09 PM on June 4, 2011: member

    Yes, setautocommit false stores txes in a temporary map local to rpc.cpp (static std::map<uint256, CWalletTx> mapTempTransactions; static std::map<uint256, CReserveKey> mapTempPoolKeys; ) so those will not touch wallet until committransaction is called.

  4. Make the fee error/dialog messages much clearer. 32abc78544
  5. Update fee policy to be much more customizable.
    This changes nTransactionFee into nBaseTransactionFee and
    nPerKBTransactionFee where nBaseTransactionFee is applied to each
    transaction once and nPerKBTransactionFee is applied per KB to
    each transaction.
    
    Also, fOverrideTransactionFee has been added to allow the ignoring
    of GetMinFee() when creating transactions.
    e76d9ebabc
  6. jgarzik commented at 8:39 AM on June 14, 2011: contributor

    A lot of good stuff in here, but

    • standard (but BIG) usability problem: if we make it easy for users to ignore recommended fee, then we just made it very easy to create transactions that may /never/ confirm. "unspending" is a very hard problem and not implemented, so any feature that makes it easy to create "limbo coins" becomes a support nightmare once users who do not know what they're doing un-check that box.

    Also,

    • should be separated into multiple pulls
    • changes fee behavior, and should be dicussed with community
  7. TheBlueMatt commented at 4:07 PM on June 14, 2011: member

    True, maybe that option should be removed and just the first and second commits suggested. Also, Im too lazy to do multiple pulls, and this was specifically written so that it does not change any fee behavior, only make it more customizable....plus it seems like the community never feels like discussing pull requests, only crazy theoretical problems that never make any sense to begin with.

  8. Add setautocommit, reject transaction and committransaction.
    Here is the help for setautocommit:
    If <autocommit> is false, the send* functions will return a txid,
    which must be manually committed instead of being immediately committed.
    Once a new transaction has been created, you can get information about it by using
    gettransaction <txid>. It can then be commited or rejected using
    committransaction <txid> or rejecttransaction <txid> respectively.
    5350a907a5
  9. TheBlueMatt commented at 2:20 PM on June 30, 2011: member

    Closing this due to several bugs found that I dont have time to fix nor the desire to fix. Going forward I'd like to see: 2. as part of a larger upgrade to fees, which Im sure it will be.

    1. probably never, though the part which upgrades the various info in the options page might be helpful as its much clearer.
    2. whenever I get the chance to rebase onto master, this might be useful for various uses in the future.
  10. TheBlueMatt closed this on Jun 30, 2011

  11. sipa referenced this in commit 9177950c74 on Oct 21, 2015
  12. sipa referenced this in commit f4787d1caf on Oct 21, 2015
  13. sipa referenced this in commit 6557a8cd46 on Oct 26, 2015
  14. sipa referenced this in commit ea06490d14 on Oct 27, 2015
  15. sipa referenced this in commit 003bb87153 on Nov 5, 2015
  16. sipa referenced this in commit bfd83199c3 on Nov 11, 2015
  17. sipa referenced this in commit b437ea7ec9 on Nov 12, 2015
  18. sipa referenced this in commit 1d84107924 on Nov 12, 2015
  19. jtimon referenced this in commit 91ee21c024 on Mar 11, 2016
  20. rebroad referenced this in commit 40ead34fbe on Dec 7, 2016
  21. deadalnix referenced this in commit a7b046e554 on Jan 19, 2017
  22. ptschip referenced this in commit 02ad5ea8d2 on Feb 9, 2017
  23. CodeShark referenced this in commit 9070b0c4ce on May 4, 2017
  24. destenson referenced this in commit 3a6dd3ee64 on Nov 18, 2017
  25. classesjack referenced this in commit 54366b8693 on Jan 2, 2018
  26. Losangelosgenetics referenced this in commit 5e992de026 on Mar 12, 2020
  27. hebasto referenced this in commit 77e23ca945 on Aug 11, 2021
  28. 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-24 15:16 UTC

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