In EstimateFee, we accept a minFeeRateNanosPerKB, but we were ignoring it if the fee estimators returned a higher fee. This was much less useful than using the minFeeRateNanosPerKB as a straight-up override so I changed the behavior there. Doing this made it so that my script was able to blast the mempool with txns, with a custom fee rate, without any reordering issues (because all the txns were being put in the same fee bucket). Eventually, we should probably change the name of this field to something like overrideFeeRateNanosPerKB but I think it's fine for now.
Followup PR from https://github.com/deso-protocol/core/pull/1252
minFeeRateNanosPerKB
, but we were ignoring it if the fee estimators returned a higher fee. This was much less useful than using the minFeeRateNanosPerKB as a straight-up override so I changed the behavior there. Doing this made it so that my script was able to blast the mempool with txns, with a custom fee rate, without any reordering issues (because all the txns were being put in the same fee bucket). Eventually, we should probably change the name of this field to something likeoverrideFeeRateNanosPerKB
but I think it's fine for now.