That's a great point and useful suggestion. But wouldn't be risky to use a static address? As loop static new gives a permanent on-chain deposit address (2-of-2 taproot: one key yours, one Loop's). This is a pre-funding box, not an actual swap. From my innerstanding, the flow would work like this:

• Send onchain sats to it any time, in any amount, in multiple deposits, especially during a low-fee period. Channels aren't touched yet.
• Later, loop static in --all converts those confirmed deposits into channel balance instantly (no waiting on a new onchain tx to confirm).
• Deposits expire after ~14,400 blocks (~100 days) and are withdrawable anytime; the swap needs your L402 token in ~/.loop.

The other point you mention is about automaticly refill channel liquidity, I found two ways to do it:

1. Automate the funding by keeping the address pre-filled: exchange auto-withdraw to the static address, or a cron/systemd job that sweeps your cache wallet when feerate is below a threshold (buy deposits when the mempool is quiet).
2. Automate the swap using loopd to refill the channel itself, funded from those deposits:

   loopd --experimental
   loop setparams --autoloop=true --type=in --loopinsource=static-address
   loop setrule <channel-id> --outgoing_threshold=30
   loop setparams --autobudget=100000 --autobudgetrefreshperiod=604800s

Now whenever a channel's outbound liquidity drops below your threshold, loopd should fire a loop-in automatically from the static deposits. --loopinsource=static-address is the piece that ties them together.

Note: This is currently an experimental feature, use at your own risk.

@AuthenticityBTC how else would you do it?