Open
Description
There are many directions we could take the autoloop feature in. This issue outlines a few features that could be implemented in upcoming iterations.
Please comment if a specific feature would be helpful for your usecase, or you would like to request a feature that is not listed.
Liquidity Management
- Per-peer rules: rather than setting a liquidity thresholds on a per-channel basis, specify a desired liquidity balance per-peer
- Flow awareness: track lnd's sends/receives/forwards and inform autoloop's swap decisions based on htlc flows
- Custom swap amounts: allow user-set minimum and maximum swap amounts
- Auto-loop-in: add support for automated loop in
Control
- Recurring budget: add a recurrence period for budget which will automatically roll over (eg, weekly/ monthly budget)
- Param handing: read parameters in from loop config, store on disk so they persist across restarts
- Batching: to save on fees, set autoloopers to execute at set times to take advantage of the server's ability to batch swaps
- Amount based backoff: if an auto-out fails due to off-chain routing, a smaller amount is likely to succeed, adjust accordingly