You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In CLN >24.08, the listconfig structure has changed causing peerswap to misread the allow-deprecated-apis field as false.
When that field is set to false, peerswap exits and print a log message explaining why. Since peerswap can't currently read the new API structure, it will always exit. We should update how peerswap (or more appropriately glightning?) reads CLN's listconfig.
"Instead of direct members with names equal the config variable, there's now a configs sub-object containing a member with details of each config setting1"
In CLN >24.08, the
listconfig
structure has changed causing peerswap to misread theallow-deprecated-apis
field asfalse
.When that field is set to false, peerswap exits and print a log message explaining why. Since peerswap can't currently read the new API structure, it will always exit. We should update how peerswap (or more appropriately glightning?) reads CLN's
listconfig
."Instead of direct members with names equal the config variable, there's now a
configs
sub-object containing a member with details of each config setting1"Footnotes
https://docs.corelightning.org/docs/deprecations ↩
The text was updated successfully, but these errors were encountered: