Conversation
nPayFee is more than intended if nBytes is exactly in multiples of 1000 bytes
|
Would changing this to /1023 instead of /1000 result in faster code as the compiler could reduce this to a series of bit shifting operations? |
|
@Gabrola What makes you think it's more than intended? @NanoAkron It'd need to be /1024 |
|
@NanoAkron If you meant 1024, that still wouldn't work on really large transactions since the rule is 1,000 bytes not 1kB |
|
@Gabrola My question is why you think it should be * 1. |
|
The transaction relay rule states: I don't think this implies that 1,000 bytes should round up to a 20,000 satoshi fee as well. |
|
Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/6166d342ad6db2ffff101f70268d17e91de1d117 for binaries and test log. |
|
Is this consistent with the transaction selection in the mining code? |
|
I just checked and it's not consistent with GetMinFee() |
|
That's not worth it IMO. The fees system is being reworked any way with floating fees. As long as GetMinFee and the wallet are consistent, it's fine at it is. Thanks for checking. |
nPayFee is more than intended if nBytes is exactly in multiples of 1000
bytes