Core Lightning

This commit is a routine feature addition to the Rust plugin library used with Core Lightning. It lets plugin authors describe hook ordering and message filters when registering hooks with the lightning node. There is no indication this fixes a security bug or introduces a vulnerability; it is an API enhancement.

This commit is a straightforward performance optimization for the JSON message decoder used in Core Lightning's Rust components. It replaces a separator-search helper that scanned from the beginning of the buffer every time with a decoder that remembers where it left off, so it does not re-examine bytes it already checked. There is no security-relevant change here: the message-splitting rule (two consecutive newlines) and the UTF-8 validation remain exactly the same.

This commit fixes a documentation typo in the Fedora install instructions. It swaps two group names to their modern DNF identifiers and adds a missing Python package (python3-mako) needed for building. There is no code change and no security issue.

This commit renames the 'currencyrate' plugin to 'cln-currencyrate' and renames its configuration options from generic names like 'add-source' and 'disable-source' to 'currencyrate-add-source' and 'currencyrate-disable-source'. It is a naming cleanup change across build files, generated RPC/protobuf code, documentation, and tests. There is no security fix or vulnerability patch in the visible diff.

This commit is a documentation-only change. It adds a list of default currency conversion data sources to the manual page for the lightningd configuration. There is no code change and no security relevance.

This commit introduces a brand-new optional Rust plugin called 'currencyrate' that adds a currency conversion API to Core Lightning. It also updates generated RPC, gRPC, and configuration schema files to expose the plugin's settings. There is no indication in the commit that this fixes a security bug; it is a feature addition.

This commit rewrites the currency-rate plugin in Core Lightning so it no longer fetches fresh exchange rates on every request. Instead, it starts a background updater that keeps a longer-lived cache and only consults extra sources if prices from different sources drift too far apart. The change also normalizes currency codes to uppercase, rejects zero prices, adds source failure backoff, and stops background tasks when a currency hasn't been requested recently. There is no explicit security bug being fixed; it is a reliability and resource-usage improvement.

This commit removes two redundant steps from the project's automated testing workflow. The removed steps manually installed Bitcoin Core (bitcoind), but the setup script already handles that installation and uses caching. There is no security-relevant change to the software itself or to how users interact with it.

This commit only renames a GitHub Actions CI job from 'Compile CLN ${{ matrix.cfg }}' to 'Build ${{ matrix.cfg }}' so the job name fits better in the GitHub web interface. It does not change any compiled code, build commands, dependencies, or runtime behavior.

This commit simply turns off a test-reporting feature in the project's automated build system because it was making tests run very slowly and the reporting server appeared to be down. It does not change any wallet, network, or Lightning protocol code, and there is no security issue in the change itself.

This change only speeds up the project's automated testing by caching downloaded software packages (Bitcoin/Elements binaries, the protoc compiler, and Linux apt packages) between CI runs. It does not alter the Core Lightning node software that users run, does not change network or wallet behavior, and introduces no obvious security vulnerability.

This commit only changes a CI (continuous integration) setup script to add debugging output to package installation commands. It is not a security fix and does not change any production code, wallet logic, or network behavior. The change is purely operational: removing the quiet flag and adding apt debug flags to diagnose why CI builds sometimes hang.

This is a routine speed-up change to the project's automated build script. It removes an unused user account creation step and installs a small tool called 'eatmydata' earlier so the rest of the package installation runs faster. There is no security issue visible in the change.

This commit is a minor test-suite cleanup. It moves a check for packet-capture tools (dumpcap/tshark) so it only runs when a specific test actually needs it, instead of running once for every test session. There is no security issue here.

This commit changes a GitHub Actions CI workflow so that one of the automated test jobs compiles the project with a higher compiler optimization level (-O3) to make the build finish faster and avoid hitting a 2-hour timeout. It does not change any production code, user-facing behavior, or security-sensitive logic.

This commit only changes two lines of documentation text in JSON schema files. It corrects the description of the 'ping' command to say it works with any currently connected peer, not just peers with an open payment channel. There is no code change and no security impact.

This commit simply adds a new build-generated executable name to the .gitignore file in the lightningd directory. It tells Git to ignore the compiled `lightning_gossip_compactd` binary so it is not accidentally committed to the repository. There is no code change, no security fix, and no vulnerability.

This commit adds a new optional 'channel_id' filter to the listpeerchannels RPC command in Core Lightning. It lets users look up a channel by its funding-transaction identifier when the short channel ID isn't yet known. The change is purely a usability/API enhancement and does not appear to fix or introduce any security issue.

This is a minor GitHub Actions CI workflow change. It switches a temporary directory used during automated testing from a shared system folder (/tmp/old-cln) to a local folder (old-cln) in the CI runner's working directory. There is no security vulnerability or user-facing change.

This commit only adds a 'slow_test' marker to an existing test. The test was sometimes failing under valgrind because the simulated network was too slow and a multi-part payment timed out before the test could complete. This is a test-suite reliability fix, not a security fix in the actual lightning node software.

This commit changes one line in the project's automated testing configuration. It switches the Liquid integration tests to use a faster compiler optimization setting (-O3) so the tests finish sooner. It does not change any code that runs in production, does not fix a bug, and has no security relevance.

This commit only reorganizes the project's automated continuous integration (CI) testing pipeline. It splits a long-running test job into six smaller parallel jobs and makes the remaining full tests depend on those finishing first. There are no changes to the actual Core Lightning software, its configuration, or how it handles user data or network traffic.

This commit only changes the project's GitHub Actions CI workflow. It switches the test artifact format from .tar.bz2 to .tar.gz, adds flags to prevent unnecessary rebuilds when running tests on prebuilt binaries, and cleans up some matrix configuration. There is no change to the actual Core Lightning software that users run, and nothing in the commit suggests a security fix or vulnerability.

This commit is a minor cleanup of the build system for Rust-based plugins. It replaces several repetitive copy rules with a single pattern rule and marks the original compiled plugin files as intermediate build artifacts so they can be cleaned up automatically. There is no change to the actual plugin code, behavior, or security of the software.

This commit only changes build-system instructions (Makefiles). It tells the build process that certain temporary files (intermediate build artifacts like generated source files and compiled library objects) can be deleted automatically after they are no longer needed, so they don't have to be bundled in release packages. There is no change to the actual Lightning node software, its networking, cryptography, or wallet logic, and no security-relevant behavior is introduced or fixed.