v0.5.0

Added

• new custom rule variable cln_multi_channel_count to restrict the number of multiple channels per peer
• new boolean option to leak the reason in the reject message: clnrod-leakreason, defaults to false
• method usage returned by lightning-cli help
• defaults for options returned by lightning-cli listconfigs
• clnrod-testping also returns the median ping

Changed

• empty clnrod-denymessage no longer allowed, please let your peer know it's not a lightning bug
• clnrod-testping now connects automatically to the peer
• clnrod-testping length argument now defaults to clnrod-pinglength
• all ping measurements were subtracted by a rpc delay amount but after pings started working properly in 25.09 it turns out this would lead to unrealistically low pings, so i removed that and as a result pings might be slightly higher now

Fixed

• cache invalidation bug: multiple quick (within 1 hour) opening attempts from the same peer with different opening specific data (e.g. different their_funding_sat) would use the oldest value from cache

Release binaries info

• Release binaries were built using rust 1.90.0
• Linux release binaries require glibc>=2.31

v0.4.3

Added

• added node alias to all notifications if available

Release binaries info

• Release binaries were built using rust 1.90.0
• Linux release binaries require glibc>=2.31

v0.4.2

Changed

• upgrade dependencies

Release binaries info

• Release binaries were built using rust 1.85.0
• Linux release binaries require glibc>=2.31

v0.4.1

Changed

• upgrade dependencies

Release binaries info

• Release binaries were built using rust 1.83.0
• Linux release binaries require glibc>=2.31

v0.4.0

Added

• new custom rule variable ping: check the time it takes to send a clnrod-pinglength bytes 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-testping pubkey [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

Release binaries info

• Release binaries were built using rust 1.82.0
• Linux release binaries require glibc>=2.31

v0.3.0

Added

• nix flake (thanks to @RCasatta)

Changed

• updated dependencies to fix dependabot alert for quinn-proto

Release binaries info

• Release binaries were built using rust 1.81.0
• Linux release binaries require glibc>=2.31

v0.2.1

Changed

• clnrod-denymessage defaults to CLNROD: Channel rejected by channel acceptor, sorry! now, because an opener could mistake an empty message for lightning being broken.

Release binaries info

• Release binaries were built using rust 1.78.0
• Linux release binaries require glibc>=2.31

v0.2.0

Added

• Collected data appended to email body
• clnrod-testrule: also sending an email if configured

Fixed

• clnrod-testrule: clear cache for tested pubkey first, so we fetch new data for a different custom rule
• cln_node_capacity_sat: was in msat precision internally
• Correctly deserialize Amboss API's empty strings for amboss_has_telegram as not having a telegram handle

Changed

• 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-reload now only reloads the content of your allowlist.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

Release binaries info

• Release binaries were built using rust 1.78.0
• Linux release binaries require glibc>=2.31

v0.1.0

Added

• initial release

Release binaries info

• Release binaries were built using rust 1.78.0
• Linux release binaries require glibc>=2.31