Follow up to #16257, this PR makes bumpfee
aware of -maxtxfee
.
It also prevents dangling locked unspents when calling fundrawtransaction
- because the previous check was after LockCoin
.
tACK a2f23b8
This also makes the QT message the same as RPC.
Afaik there’s no way to reach the A fee higher than %1 is considered an absurdly high fee
message anymore, so should we get rid of that string and Reject absurdly high fee
in walletmodel.cpp
?
3129@@ -3135,6 +3130,11 @@ bool CWallet::CreateTransaction(interfaces::Chain::Lock& locked_chain, const std
3130 }
3131 }
3132
3133+ if (nFeeRet > this->m_default_max_tx_fee) {
style-nit:
0 if (nFeeRet > m_default_max_tx_fee) {
m_
already means this->
, no need for duplicate.
3129@@ -3135,6 +3130,11 @@ bool CWallet::CreateTransaction(interfaces::Chain::Lock& locked_chain, const std
3130 }
3131 }
3132
3133+ if (nFeeRet > this->m_default_max_tx_fee) {
3134+ strFailReason = TransactionErrorString(TransactionError::MAX_FEE_EXCEEDED);
Concept ACK.
Maybe revert the docstring in the gui to say “belt-and-suspenders” again?
See https://github.com/bitcoin/bitcoin/pull/16257/files#diff-2e3836af182cfb375329c3463ffd91f8
Thanks for the sendmany
and fundrawtransaction
RPC tests @MarcoFalke.
Maybe revert the docstring in the gui to say “belt-and-suspenders” again?
Maybe that is indeed slightly safer than dropping it completely.
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
No conflicts as of last run.
ACK 9ff66a1b2157bcce8ccd4cea0610eae79d0be6d8 (read code, wrote test case)
Signature:
0-----BEGIN PGP SIGNED MESSAGE-----
1Hash: SHA512
2
3ACK 9ff66a1b2157bcce8ccd4cea0610eae79d0be6d8 (read code, wrote test case)
4-----BEGIN PGP SIGNATURE-----
5
6iQGzBAEBCgAdFiEE+rVPoUahrI9sLGYTzit1aX5ppUgFAlwqrYAACgkQzit1aX5p
7pUhCrQv8C829o7ZZs8hUWaldWPLHQdivLOKMhyEC24GVjlOb2CPwh+YDSs4bZUNj
8qVpgveclR55eb9j4tj7Wt+4AqNiNeHyKMgNfXCXeWKj4CYDSGRfwd1zpSnL8Z/Lk
9cXyp2AV5GcSX3hjG/1tbFphxDYLoiihfSLMVTGybC4aNupxqIiAFRPBVS9ovwHBA
10Ml3r9H0CueguuZMR1m2B/hxA+fOWe19VxCck93dydfL7v+N56tvatm/+5ihwaXAf
11v3wwrHHdA2j0i3yXOSCdDezC0arwA3CMVJWZNt5rJt2ydLG46YSp7S4XwjpJD36V
12G04nwXgfIRv9HPPeYLESOQHf/RiGQaaC4TRLuxPo3P/abhzXq2ucSTdsm0mtqeuj
13pTdasa8y6fAWs4Y//y84ce28bbLpWwM1QHCbf1GwemqNhXpxOwZnk6uAqwM+2D6v
14SJ0hV5HqocIfbUM1WKqBnKpLnvHicvPeMOjTtQw3g1KHvhY9DCK9tAX1vYom2qDd
15Y5xHfFCm
16=I+BI
17-----END PGP SIGNATURE-----
Timestamp of file with hash e8c4afba47440f5e82e36c70bed731c61cc784c18d70774903ee95050752dbfa -
utACK 9ff66a1b2157bcce8ccd4cea0610eae79d0be6d8
Looks good. Was wondering about the two test commits, until I realized author was different.
60+ -4,
61+ "Fee exceeds maximum configured by -maxtxfee",
62+ lambda: self.nodes[0].fundrawtransaction(hexstring=raw_tx),
63+ )
64+
65+ self.log.info('Check maxtxfee in combination with settxfee'.format(fee_setting))
.format(fee_setting)
part is a mistake? :-)
re-ACK 0d101a340c44841cbbc5982d55354b1787bc39e2, only change is small test fixup
Signature:
0-----BEGIN PGP SIGNED MESSAGE-----
1Hash: SHA512
2
3re-ACK 0d101a340c44841cbbc5982d55354b1787bc39e2, only change is small test fixup
4-----BEGIN PGP SIGNATURE-----
5
6iQGzBAEBCgAdFiEE+rVPoUahrI9sLGYTzit1aX5ppUgFAlwqrYAACgkQzit1aX5p
7pUgQbwwAtg+GMzWeDLh1+NCCGz5Bs6tmgzthA2R28KiIaoQsgivJMdd2FoOMl7/C
8dlKZ7gKbttnEtr/Rl4pFALzy9L8oMiFmoXC+qy3APx4Z3Xd+MS4aLM1WqxHggkPN
9u6679W5/OtN4UE6oksKGM84EOAfKqSCHG/cZqGJ8a4UCIZWku2EhHiqo16gaNJvi
105MNuaIQjpGqQf5egbqV+lWIvJmnHXzoIKN09Eo7PS7PwtCJy6A1x8uy12CxsU6G3
11Dl8M27a52PNvoXHeWX+xyKlbDIFSOf9vuc4/bP/ylMtC7vIGdO/W0SIyvsaNMLHq
12+cOAJZxLoxZKgK2VUQqxH1L/VafPtm/a2v23LzkUFoK7Vk0fENekpuiQTZsDRQV8
13OOXhf7TFukNGVCS60tBJa1Mf0LrSfT3DgV/NNVni1YYDg97H6tX0lpXQyJ8LSZg5
14o8dWBno9MWsoFAyAfsPxWtS9FI7xLb1XuYMiMNBdF2FGikHIebt9R5CJqfGVIgoc
159IJFNrPA
16=Cuz4
17-----END PGP SIGNATURE-----
Timestamp of file with hash a2d0938771647864e65f9d3c8939d69334e4a3be00ac928e24814e25e15140d2 -
promag
Sjors
MarcoFalke
DrahtBot
laanwj
kallewoof
practicalswift
fanquake
Labels
Wallet
Milestone
0.18.1