I agree, the risk of going over max reward should be sufficient to prevent the creation of excessively large block sizes. I would also like to have the set values persist through wallet restarts as it is a pain to have to repeatedly set these values whenever there is a need to restart the wallet.
what pain ? 2 lines in conf and you'r done
It would be great if that worked. It does not. Nor does it work as a command line option. At least not under Win7
works for me it seems.
ok, if not, 2 lines in a batch file using curl
If the maximum you are attempting is not very big, then the settings you are describing work. But at least at the time I tried it, the maximum values allowed using those settings did not allow any where near the amounts I am able to set the threshold(s) too after the wallet is running.
There was in fact a way to use command line and/or .conf settings to set a higher (but not much higher) value when I originally attempted to automate it, The problem at the time was that the maximum acceptable values used at wallet startup were much lower than what a larger stakeholder was able to set the values to after the wallet was running. It seems like the startup maximum was something like 200 HBN which is kind of like "why bother" raising it from the default value of 5 at all. Larger stakeholder were able to set the value much higher than 200 (based upon total HBN in wallet) but only after the wallet was up and running.
This may have changed in a subsequent wallet release and when I get a little time I will see if setting those values again allows for a more reasonable max threshold at startup.