forked from dashpay/dash
-
Notifications
You must be signed in to change notification settings - Fork 719
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge #1641: [Core] New fee estimation code
4038de4 [QA] Restore 'feature_fee_estimation.py' functional test (random-zebra) 988f349 [qt] Properly display required fee instead of minTxFee (random-zebra) c5c9df0 [Trivial] Fix typos (random-zebra) a8fa99b [Trivial] Remove redundat check in ContainsZerocoins (random-zebra) 8ebcbcd PolicyEstimator: exclude zerocoin spends when computing estimates (random-zebra) b67049b Create new BlockPolicyEstimator for fee estimates (random-zebra) Pull request description: This introduces the new fee and priority estimation code described here <https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg06405.html>. Instead of calculating the median fee for each possible number of blocks needed to confirm, the new code divides the possible fee rates into buckets (spaced logarithmically) and keeps track of the number of blocks needed to confirm for each transaction in each bucket. Backports: - bitcoin#5159 - bitcoin#6887 except for the functional test (`smartfees.py`) which is based on an older version of the framework. Instead I've restored a more recent `feature_fee_estimation.py` (commenting out the check for `estimatesmartfee` which can be reintroduced once bitcoin#6134 is backported). Additional commits exclude zerocoins txes from the estimates calculation, as they have fixed fee/priority. ACKs for top commit: Fuzzbawls: ACK 4038de4 furszy: ACK 4038de4 and merging Tree-SHA512: 25777af469f7fa84d2dab991544392bea8418bccb4d2c23113de2c6ed7047891bdaedad1728cb04ba343e82f4bc0c1446f88e28def698dd25168769abf8620bb
- Loading branch information
Showing
18 changed files
with
1,106 additions
and
368 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.