Core Lightning on September 16 advised node operators with experimental features enabled to disable them immediately while developers investigate issues that could affect user funds. The alert, reported by Gate News, narrows the immediate concern to users running those optional features rather than to all Core Lightning operators.
Core Lightning tells experimental-feature operators to disable them
The project’s warning did not identify the issues under investigation or quantify any potential exposure. It directed operators who had enabled experimental functionality to disable it, citing the concern that the issues could affect user funds.
Core Lightning is implementation software for the Bitcoin Lightning Network, where node operators can choose from configuration options that include features still being tested. The September 16 notice makes those opt-in settings the focus of the current precaution.
StartOS users told to disable dual funding and liquidity ads
For affected Core Lightning users on StartOS, Start9 recommended disabling “Dual funding and liquidity ads,” according to the Gate News report.
The recommendation is a precaution while the investigation continues. It identifies the StartOS configuration covered by the guidance and is consistent with Core Lightning’s broader instruction to disable experimental features.
It does not, by itself, establish that dual funding or liquidity ads caused the issues under investigation.
Warning follows v26.06.7 vulnerability disclosure
The alert comes five days after Core Lightning published the previously embargoed source code for v26.06.7. In its September 11 release notice, the project said the version fixed confirmed vulnerabilities reported by multiple sources.
Core Lightning’s own configuration documentation says experimental options are intended for advanced users testing proposed features and may break between releases. Experimental dual funding is specifically listed among those options.
That documentation provides the relevant operating context for the latest warning: the feature class now singled out for disabling was already designated as potentially breakage-prone, while developers investigate the newly reported risks to funds.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
