Core Lightning

This commit only adds documentation comments quoting the BOLT (Basis of Lightning Technology) specification and explaining how the existing code follows it. It does not change any program logic, function behavior, or security controls. A few comments note that the current implementation is incomplete ("FIXME"), but those are observations, not fixes. There is no evidence this commit addresses a security vulnerability or changes anything an attacker could exploit.

This commit only adds missing BOLT (Bitcoin Lightning specification) quote references inside code comments across 12 files. There are no code behavior changes, no bug fixes, and no security fixes. It is a documentation-only cleanup.

This commit tightens the rules for when a Lightning node rejects a fee-rate change from the other party. It now skips certain 'dust exposure' checks when a modern anchor-based channel is in use, and only checks the remote side's dust exposure when the fee is actually increasing. This aligns the code with the final version of a published protocol specification change (BOLT PR 919). The change is defensive: it reduces the chance that a peer can force your node to close a channel by manipulating fees, but it is a partial patch that only updates one of the places where dust limits matter.

This commit only updates comments and documentation strings in Python test and library files to match the current wording of the BOLT (Basis of Lightning Technology) specifications. It changes punctuation, capitalization, field ordering in invoice breakdowns, and backtick formatting. No executable code behavior is changed, so there is no security impact.

This commit updates code comments that quote the Lightning Network specification (BOLT) in four files. Most changes are cosmetic: fixing outdated wording, malformed quote markers, and removing one incorrect quote. One change in connectd/queries.c removes a stale BOLT requirement comment but does not alter the actual behavior, which already replies with sync_complete=false for an unknown chain. Another change in dual_open_control.c updates a comment about what to do when a transaction's effective feerate is too low, but the surrounding code still calls a failure path. Overall, the commit is primarily documentation cleanup and does not appear to introduce or fix a security vulnerability on its own.

This commit fixes a rounding bug in Core Lightning's splice commands. Previously, when reading a channel balance expressed in milli-satoshis (msat), the code rounded to the nearest whole satoshi. Now it always rounds down. The change removes two test markers that expected the old behavior to fail, suggesting the bug was causing real splice-in/splice-out failures when balances had fractional satoshis.

This commit only adds two new automated tests for a feature called 'splice scripting' in Core Lightning. The tests check how the software handles very small fractional bitcoin amounts (millisatoshis) during channel splicing. There is no change to production code, no bug fix, and no security patch.

This is a minor build-compatibility fix for the GCC 15 compiler. It changes two local variables from `char *` to `const char *` so the code compiles cleanly with newer, stricter compiler warnings. There is no functional change and no security impact.

This commit adds a new diagnostic feature: it lets Core Lightning send internal tracing data (timing and span information) over a local Unix Domain Socket, and it makes the tracing code always compile even when USDT probes are not available. It is a feature/refactoring patch, not a security fix. There is no indication it addresses a vulnerability.

This commit only updates developer documentation. It describes a new Unix Domain Socket tracing backend and lists environment variables. There are no code changes, no bug fixes, and no security-related modifications.

This commit adds a new automated test that checks whether Core Lightning can send tracing data over a Unix domain socket. It is purely a test file change and does not modify any production code, configuration defaults, or network behavior. There is no security-relevant change.

This commit is a minor GitHub Actions workflow update. It tells the project's automated documentation checker to also run when JSON schema files inside two new subdirectories ('hook' and 'notification') are changed. There is no change to the actual Lightning node software, no user-facing behavior change, and no security relevance.

This commit fixes a flaky automated test in Core Lightning. The test was occasionally failing because of tiny floating-point rounding differences when calculating transaction fees, not because of a real bug or security issue. The change replaces a strict hand-rolled tolerance check with a more forgiving helper function already designed for this purpose. There is no security impact.

This commit only updates the CHANGELOG.md file for the v26.04.1 release. It does not change any source code, so it cannot introduce or fix a security vulnerability by itself. The changelog text mentions fixes for a gossip protocol issue and several build failures, but those actual code changes are in other commits/pull requests, not in this diff.

This commit fixes the type of placeholder used in debug log messages when printing transaction weight values. On some platforms, using the wrong placeholder can cause the program to crash or print garbage when logging is enabled, but it does not create a security vulnerability that an attacker can exploit. It is a build/robustness fix, not a flaw in transaction handling itself.

This commit fixes a build problem on 32-bit ARM computers by removing the use of a 128-bit integer type that those systems do not support. It changes one currency-conversion calculation in the bookkeeper plugin to use ordinary 64-bit math with a floating-point fallback, and adds a test file to check the results. There is no direct security vulnerability being patched; it is primarily a portability/build fix.

This commit is a documentation-only change for the Core Lightning project. It updates the build system and scripts so that notification and hook documentation is automatically generated from JSON schemas and published to the project's ReadMe.com documentation site. It removes large manually-written sections from two developer guide pages and replaces them with links to the auto-generated documentation. There is no change to the actual lightning node software, its network behavior, or its security-sensitive logic.

This commit is a documentation and schema cleanup. It fixes formatting in JSON schema files so they render correctly as Markdown, removes redundant 'added' version labels from nested schema fields, corrects some labels from 'notification' to 'hook' where the schema describes a hook, and adds a small clarification to the shutdown notification description. There are no code changes that affect how Core Lightning processes payments, channels, or peer messages.

This commit removes an unmaintained Rust helper crate called `paste` from the LSPS plugin and replaces its macro-generated function names with manually written ones. There is no functional change to the program's behavior, no bug fix, and no security patch. It is a routine dependency cleanup.

This commit is a routine bulk upgrade of Rust third-party libraries to versions compatible with Rust 1.85. The changes are mostly mechanical adaptations to new library APIs: certificate signing now uses an 'Issuer' object instead of separate certificate and key, gRPC/protobuf code generation moved to new 'tonic_prost' crates, and the random-number generator name changed from OsRng to SysRng. There is no explicit security fix or vulnerability disclosure in the commit message or diff, but dependency upgrades can indirectly affect security by picking up upstream bug fixes or, conversely, introducing new bugs.

This commit changes how log messages are collected from Rust tracing events in the cln-plugin library. Previously, only the main message text was captured. Now, extra structured fields attached by logging dependencies are appended to the message, while internal metadata fields like file and line number are filtered out. This is a feature enhancement to improve log readability and avoid duplicate metadata, not a security fix.

This commit only adds JSON documentation schemas for existing plugin hooks. It does not change any executable code, runtime behavior, or security logic. It is a documentation-only change that describes what data plugin hooks already send and receive.

This commit is a code-generation tooling change for Core Lightning. It extends the existing message generator (msggen) to also produce Rust data structures for plugin hooks, and adds the generated file cln-rpc/src/hooks.rs. It does not change how the node processes payments, channels, or RPC commands; it only adds type definitions and tests so that Rust code can more easily deserialize hook events and actions. There is no indication this fixes or introduces a security vulnerability.

This commit adds new Rust types and matching gRPC protobuf messages for carrying arbitrary JSON data (objects, arrays, and scalar values) through Core Lightning's RPC and plugin interfaces. It is a pure infrastructure/serialization change with no security-relevant behavior visible in the diff.

This commit adds new convenience methods to the Core Lightning plugin library in Rust. It lets plugin authors register 'hooks' (callbacks triggered by the lightning daemon) using typed request/response structures instead of raw JSON. The change is purely additive and does not fix any known bug or vulnerability.