rust-lightning

This commit is purely a code-formatting cleanup. It removes a #[rustfmt::skip] directive and lets the Rust formatter rewrap the internal_splice_init function and its call sites. No logic, behavior, or security checks were changed.

This commit is purely a code-formatting cleanup. It removes a `#[rustfmt::skip]` directive and lets Rustfmt reformat the `internal_commitment_signed` function in the Lightning channel manager. No logic, behavior, or security properties of the code are changed.

This commit is purely a formatting cleanup. It removes a #[rustfmt::skip] annotation and lets the Rust formatter reformat the internal_tx_abort function. No code behavior, logic, or security properties were changed.

This commit is purely a code-formatting cleanup. It removes a #[rustfmt::skip] annotation and lets Rustfmt reformat the internal_splice_ack function in the Lightning channel manager. No logic, behavior, or security properties of the code were changed.

This commit is purely a code-formatting cleanup. It removes a manual 'do not format' marker from one function and lets the Rustfmt tool reformat the code. No logic, behavior, or security properties of the software were changed.

This commit is purely a code formatting cleanup. It removes a #[rustfmt::skip] annotation and lets the Rustfmt tool reformat the internal_tx_complete function in the Lightning channel manager. No logic, behavior, or security properties of the code were changed.

This commit is a straightforward internal cleanup: it replaces several copies of the same error-message formatting code with a single shared helper. The actual error type returned to callers (APIError::ChannelUnavailable) and the information included in the message remain the same. There is no security fix or behavior change.

This commit is a straightforward code cleanup: it replaces repeated, copy-pasted error-message strings in Lightning message handlers with two shared helper functions. The actual error behavior and the messages returned to peers are essentially unchanged (one message now also includes the channel ID, but that is a minor informational improvement). There is no security fix or vulnerability here.

This commit prepares the Lightning Dev Kit (LDK) to support a new 'phantom node' feature for BOLT 12 offers. It changes how encrypted control data in blinded payment paths and onion messages is authenticated: instead of checking one extra node-specific key, it now checks two keys (the existing node-specific key and a new shared phantom-node key). The commit itself does not enable the actual phantom-node building logic yet, but it adds the cryptographic plumbing so that future versions can authenticate blinded paths from any participant in a phantom-node setup while still keeping normal onion messages tied to a specific node.

This commit adds a new feature to rust-lightning that lets a group of Lightning nodes create a single BOLT 12 offer that can be paid to any node in the group. It is a feature addition for 'phantom node' setups, not a fix for a known security bug. There is no evidence in the commit or supplied references that this resolves an active vulnerability or incident.

This commit adds a seventh cryptographic key to an existing key-expansion routine. The new key is intended for a future feature where multiple nodes can share a 'phantom' blinded payment path. The change itself only extends the HKDF output and stores the extra key; it does not introduce a vulnerability or fix one.

This commit changes the project's automated testing configuration so that pull requests and non-main branches only run tests on Linux with the oldest supported Rust version. The full test matrix across Windows, macOS, stable, and beta Rust versions still runs, but only when code is pushed directly to the main branch. There is no code change to the actual software and no security vulnerability is introduced by this configuration change.

This commit is a straightforward internal code refactor in the Lightning Dev Kit (LDK) library. It splits one method into three smaller, more focused methods and changes how pending payment forwarding data is organized. There is no new security vulnerability introduced; the change is preparation for a future cleanup of duplicated data fields.

This commit is a code cleanup that removes duplicated data stored when a forwarded Lightning payment is saved to disk. It does not change how payments are validated or how funds move; it only changes which fields are kept in memory versus reconstructed later. There is no direct security vulnerability visible in the diff, though any serialization change carries a small risk of compatibility bugs.

This is a minor code cleanup change inside test helper macros. It replaces short internal names like `_reload_node` with fully qualified paths such as `$crate::ln::functional_test_utils::_reload_node`. This only affects how test macros resolve symbols when reused in other test crates; it does not change runtime behavior, user-facing APIs, or any security-sensitive logic.

This commit is a minor cleanup of internal test code. It removes redundant calls that explicitly set a default test configuration for Lightning channel managers, replacing them with simpler 'None' values that now produce the same default. There is no change to production code, no security fix, and no user-facing behavior change.

This commit is a minor cleanup of an internal test file. It replaces a small block of test code with an existing helper function when testing the non-zero-conf path. There is no change to production code, no security fix, and no user-facing behavior change.

This is a small documentation and test cleanup commit. It removes leftover references to a 'manually_accept_inbound_channels' configuration option from two test files and a pending changelog entry. There is no code behavior change and no security fix or vulnerability present in the diff.

This commit removes the proptest testing library from the lightning-liquidity Rust crate because one of proptest's indirect dependencies bumped its own minimum Rust version, breaking the project's MSRV (Minimum Supported Rust Version) policy. While removing the tests, the author also fixed a subtle rounding bug in the fee calculation helper: it now uses Rust's built-in div_ceil instead of the old add-999999-then-divide-by-1000000 trick. The commit also deletes a large block of URL parsing tests. There is no direct evidence this is a security fix, but the fee rounding change is a correctness improvement and the commit message explicitly notes that the previous tests were broken on most inputs.

This commit only updates version numbers in package configuration files (Cargo.toml) for the lightning-types crate and its dependents. It does not change any actual program code, fix a security bug, or alter runtime behavior. The change was made because a previous commit modified the crate's public interface but forgot to increase the version number, causing automated semver compatibility tests to fail.

This commit fixes a bug in the Lightning Dev Kit's Tokio networking code where Tor-proxied outbound connections were accidentally advertising the Tor proxy's address as the peer's address. After the fix, the actual peer address is used instead. This is mainly a privacy and correctness issue: previously a node might leak its Tor proxy's address to the peer and misreport who it was connected to.

This commit fixes a subtle file-listing bug in the Lightning payment channel data storage code. When listing saved data, the program used to ask the filesystem for fresh details about each file, which on common Linux filesystems can briefly make a file appear missing if it is being changed at the same time. The change uses cached information already returned by the directory scan, avoiding that extra check and the race condition. It is a reliability fix rather than a direct exploit, but in the worst case it could cause the node to fail to load channel data it expected to find.

This commit is a small, internal refactoring of a Rust serialization macro used in the Lightning Dev Kit. It adds an optional read-time callback to the 'legacy' type-length-value (TLV) field variant so future code can validate or reject decoded legacy values. All existing usage sites pass a no-op callback that always succeeds, so the change does not alter current behavior. It is a defensive/extensibility improvement, not a fix for an active security bug.

This is a fix inside a single test function. The test had a tight loop that repeatedly checked for events without ever pausing, which could monopolize a lock and prevent another thread in the same test from making progress. The change adds a brief yield so the other thread can run. It only affects test code, not production code, and has no security impact on real users.

This commit only updates a code comment to clarify that the payment_preimages field also covers forwarded payments, not just inbound payments. No actual code behavior was changed, so there is no security issue or vulnerability.