diff options
author | Wladimir J. van der Laan <laanwj@protonmail.com> | 2019-09-18 16:47:23 +0200 |
---|---|---|
committer | Wladimir J. van der Laan <laanwj@protonmail.com> | 2019-09-18 16:49:18 +0200 |
commit | 0ee0474234654d1587afd5816ca6794620a11f16 (patch) | |
tree | e916bb6afda8cef3ffdd85323544bd19a8601eed /test/functional/test_framework/util.py | |
parent | dd8cf82e96042cb59354ee1677830f414a5baaaf (diff) | |
parent | 2dfd6834ef8737e16e4b96df0c459f30a0721d6c (diff) | |
download | bitcoin-0ee0474234654d1587afd5816ca6794620a11f16.tar.xz |
Merge #16521: rpc: Use the default maxfeerate value as BTC/kB
2dfd6834ef8737e16e4b96df0c459f30a0721d6c test: Add test for default maxfeerate in sendrawtransaction (Joonmo Yang)
261843e4bef96ab296a9775819a99bfa60cad743 wallet/rpc: Use the default maxfeerate value as BTC/kB (Joonmo Yang)
Pull request description:
Fixes https://github.com/bitcoin/bitcoin/issues/16382
This patch tries to treat `maxfeerate` in sendrawtransaction/testmempoolaccept RPC as a rate(BTC/kB) instead of an absolute value(BTC).
The included test case checks if the new behavior works correctly, by using the transaction with an absolute fee of ~0.02BTC, where the fee rate is ~0.2BTC/kB.
This test should be failing if the default `maxfeerate` is 0.1BTC, but pass if the default value is 0.1BTC/kB
ACKs for top commit:
laanwj:
ACK 2dfd6834ef8737e16e4b96df0c459f30a0721d6c (ACKs by Sjors and MarcoFalke above for trivially different code)
Tree-SHA512: a1795bffe8a182acef8844797955db1f60bb0c0ded97148f3572dc265234d5219271a3a7aa0b6418a43f73b2b2720ef7412ba169c99bb1cdcac52051f537d6af
Diffstat (limited to 'test/functional/test_framework/util.py')
0 files changed, 0 insertions, 0 deletions