Releases: daywalker90/clnrod
Releases · daywalker90/clnrod
v0.4.1
v0.4.0
Added
- new custom rule variable
ping
: check the time it takes to send aclnrod-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
v0.2.1
Changed
clnrod-denymessage
defaults toCLNROD: 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 rulecln_node_capacity_sat
: was in msat precision internally- Correctly deserialize
Amboss
API's empty strings foramboss_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 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
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