Is your feature request related to a problem? Please describe.
CLI based static loop ins will be easier to script/automate plus users will be able to more easily work within a budget if the max fee rate can be set via CLI
Describe the solution you'd like
expose max fee rate in CLI and add a --max_fee_rate <fee in sats and/or ppm> type argument
Describe alternatives you've considered
my auto static loop in script currently pipes "no" on the first attempt so that it can read the fee without actually performing the loop in. if the quoted fee is less than a set amount then it will perform a second attempt, piping yes to complete the loop in automatically
Additional context
the above solution appears to work but there is still room for error. mostly all of my loop ins are to my LOOP channel so the fee should be <100 sats but ive been snagged before with 40,000sat+ fees (before i implemented the check as described above)
Is your feature request related to a problem? Please describe.
CLI based static loop ins will be easier to script/automate plus users will be able to more easily work within a budget if the max fee rate can be set via CLI
Describe the solution you'd like
expose max fee rate in CLI and add a --max_fee_rate <fee in sats and/or ppm> type argument
Describe alternatives you've considered
my auto static loop in script currently pipes "no" on the first attempt so that it can read the fee without actually performing the loop in. if the quoted fee is less than a set amount then it will perform a second attempt, piping yes to complete the loop in automatically
Additional context
the above solution appears to work but there is still room for error. mostly all of my loop ins are to my LOOP channel so the fee should be <100 sats but ive been snagged before with 40,000sat+ fees (before i implemented the check as described above)