sling-inform-layers: CLN 24.11+ will inform these layers about sling's liquidity information gained by failed rebalances. Can be stated multiple times. Defaults toxpaywhich will help thexpaycommand.
sling-reset-liquidity-intervaldefaults to 60m now and checks every 2m (previously: 360m/10m). This is to be in sync with the aging ofxpay's layer
sling-refresh-peers-intervalwas not actually dynamicsling-refresh-aliasmap-intervalwas not actually dynamicsling-refresh-gossmap-intervalwas not actually dynamicsling-reset-liquidity-intervalwas not actually dynamic
sling-utf8, it was not used
- rebalances between private channels would fail after the first if only private channels are candidates
- nix flake (thanks to @RCasatta)
- optional boolean argument for
sling-statsto set output of the summary to json, e.g.sling-stats true
- updated dependencies
sling-refresh-gossmap-interval: How often to readgossip_storeupdates in seconds. Default is every10s
slingnow reads thegossip_storefile directly instead of polling the whole graph vialistchannels. This drastically reduces CPU usage on and especially after the first read. Also, sinceslingis reading incremental changes to thegossip_storefile, it can poll it much more often to keep a closer track of any gossip changes.- Options code refactored. All options are now natively dynamic and there is no longer any manual reading of config files. Read the updated README section on how to set options for more information
sling-refresh-graph-interval, replaced bysling-refresh-gossmap-interval
- Restored backward compatibility to v23.11
- When running
paralleljobs>1 there were still duplicate routes taken sometimes
- if you had the plugin with config file options start with CLN and then changed an option and only reloaded the plugin, CLN would pass stale option values to the plugin so the load priority changed to:
- config file options
plugin startoptions
- possibly fixed another rare deadlock