- new custom rule variable
ping: check the time it takes to send aclnrod-pinglengthbytes long message to the opening peer and back. Defaults to the average of 3 pings with 256 bytes length. Timeouts and errors will log but not flat out reject the channel, instead the timeout value of 5000 will be used. It is recommended to have email notifications on or watch the logs for ping timeouts (Clnrod ping TIMEOUT), since i encountered a rare case of CLN's ping getting stuck, requiring a node restart - new rpc method
clnrod-testpingpubkey [count] [length]: try the ping measurements with a few options - new option
clnrod-pinglength: set the length of the ping message for the custom rule check. Defaults to 256 bytes - more precise feedback if a custom rule rejects a peer, lists offending comparisons (non-exhaustive) that caused the rejection and their actual value
- nix flake (thanks to @RCasatta)
- updated dependencies to fix dependabot alert for
quinn-proto
clnrod-denymessagedefaults toCLNROD: Channel rejected by channel acceptor, sorry!now, because an opener could mistake an empty message for lightning being broken.
- Collected data appended to email body
clnrod-testrule: also sending an email if configured
clnrod-testrule: clear cache for tested pubkey first, so we fetch new data for a different custom rulecln_node_capacity_sat: was in msat precision internally- Correctly deserialize
AmbossAPI's empty strings foramboss_has_telegramas not having a telegram handle
- Options code refactored. All options are now natively dynamic. Read the updated README section on how to set options for more information
- Because of the above
cln-reloadnow only reloads the content of yourallowlist.txt/denylist.txt, everything else is handled by the new options code - If an API returns successfully but has no data we assume the worst values instead of throwing an error
- initial release