Core Lightning

This change adds size caps to internal queues in the Lightning node's gossip subsystem, mirroring limits that already existed for some maps. It is a hardening/DoS-prevention patch: without limits, an attacker could potentially flood the node with gossip messages and consume unbounded memory. The patch also adds a CI_UNEXPECTED marker so the continuous-integration system flags unexpected flooding. There is no direct evidence in the commit of an active exploit or a specific vulnerability being fixed beyond resource-exhaustion risk.

This commit simply removes a developer-only experimental feature flag called 'dev_uniform_padding' from an internal message definition file. It is a clean revert of a previous commit that added the flag. There is no indication this change fixes or introduces a security vulnerability; it just undoes an unmerged or unwanted development experiment related to padding network messages for traffic-analysis defense.

This commit simply reverts a previous test-only change. It removes a special developer flag ('dev-uniform-padding') from a network traffic test, returning the test to its original state. There is no change to production code, no user-facing behavior change, and no security fix or vulnerability introduced by this patch.

This commit removes a developer-only experimental feature called --dev-uniform-padding that padded peer network messages to fixed 1460-byte chunks. It is a clean revert of an earlier feature addition and does not fix any known security vulnerability. The change simply deletes the option and its wiring; no bug or exploit is present in the diff.

This commit removes a developer-only flag that made message padding optional, restoring uniform padding for all encrypted peer messages. Uniform padding hides the real length of messages, so reverting to always-on padding is a privacy improvement rather than a security bug. There is no direct evidence this change fixes an active vulnerability; it appears to be a design cleanup that strengthens traffic-analysis resistance.

This is a one-line change to a test file. It adds a developer-only flag ('dev-uniform-padding') when creating test nodes so that an existing test for constant TCP packet sizes actually exercises the uniform-padding feature. There is no change to production code, no bug fix, and no security-relevant behavior change.

This change makes a message-padding feature optional instead of always-on. The always-on padding was causing Core Lightning nodes to be disconnected by LND-based peers because it sent oversized ping messages. The fix adds a developer flag so operators can turn padding on only when all their peers support it. It is a compatibility/operational fix, not a security patch for an exploitable vulnerability.

This commit adds a new hidden developer-only command-line flag called --dev-uniform-padding. When enabled, it tells the daemon to pad outgoing peer messages to fixed 1460-byte chunks as a defense against traffic analysis. The change only wires the flag through the daemon; the actual padding logic is not present in this commit. There is no security vulnerability here.

This commit adds a new internal flag called dev_uniform_padding to a wiring definition file so two parts of the Core Lightning software can agree on whether an experimental traffic-padding feature is turned on. It is a one-line metadata addition with no executable code changes and no security fix.

This commit fixes a startup crash in Core Lightning. If the node had stored a special type of payment (a 'blinded HTLC') that needed to be replayed when restarting, the code could try to decode its encrypted onion before the secure key-handling helper was ready. The fix simply initializes that helper earlier in startup and adds a regression test. It is a reliability bug, not a code-execution or theft vulnerability.

This commit simply changes the download source for Bitcoin Core inside a Fedora build container, switching from a Google Cloud Storage bucket used by the project to the official bitcoincore.org website. There is no security-relevant code change and no indication of a vulnerability.

This commit is a minor API consistency fix. It changes the data type of the `direction` field returned by the `listpeerchannels` command from a signed 64-bit integer (`integer`/`sint64`) to an unsigned 32-bit integer (`u32`/`uint32`). The field only ever holds the values 0 or 1, so this simply aligns it with how the same field is represented in other parts of the API. It is not a security patch and does not fix a vulnerability.

This commit is a routine version bump to mark the v26.04rc1 release candidate of Core Lightning. It only updates version strings across packaging files, the changelog, a contributor credit script, and a lockfile. There are no code changes that alter how the software behaves or processes data.

This commit adjusts how often a background currency-rate updater checks exchange-rate sources. Previously, the updater slept a fixed amount between runs; now it sleeps less when there are more sources, so each source gets queried about once per hour on average. This is a performance and freshness tuning change, not a security fix.

This commit fixes a bug in Core Lightning's currency-rate plugin. Previously, when exchange-rate data was cached, the plugin used only the most recent single source instead of combining all still-fresh sources and taking the median. Using a single source makes the converted bitcoin amount easier to manipulate if one price feed is wrong or malicious. The fix restores the intended median behavior across all fresh cached prices.

This is a straightforward internal code cleanup in Core Lightning's plugin library. It changes many plugin option-parsing functions so they receive a 'command' object instead of a 'plugin' object. The commit message says this is preparation for future 'dynamic options' work (specifically for a bookkeeper currency feature). There is no bug fix, security patch, or vulnerability visible in the diff itself.

This commit changes how the command-line tool 'lightning-cli' prints JSON strings in its simple human-readable output mode. Previously, backslashes used for escaping (like \" to show a quote, or \\ to show a backslash) were left in place, so users saw extra backslashes on screen. The patch now strips the backslash for any escape it does not explicitly handle (only \n newline and \t tab are still converted). This is a display/output formatting fix, not a change to how data is parsed or stored.

This commit changes how a Core Lightning plugin stores and calculates Bitcoin exchange rates. Previously the plugin stored 'millisatoshis per fiat unit' and took the median of those inverted values. Now it stores the raw fiat price of one bitcoin and converts only at output time. The commit message explicitly notes this is a subtle change because the median of bitcoin prices is mathematically different from the median of inverted rates. The patch is described as the first step in updating the API, not as a security fix.

This commit adds a feature to the bookkeeper plugin that saves fetched currency exchange rates to the node's internal datastore so they survive restarts. It is a functionality improvement, not a security fix. There is no indication in the commit or supplied references that this resolves a vulnerability or security issue.

This commit adds a new bookkeeping command, bkpr-report, that lets users format their node's income events into custom text or CSV output. It is a feature addition, not a security fix. There is no indication in the commit or supplied references that it addresses a vulnerability or security issue.

This is a small internal code refactor in Core Lightning's currency-rate plugin. It moves the constant 'MSAT_PER_BTC' and the final arithmetic from the back-end oracle into the front-end handler, exposing a new 'get_median_rate' helper. The actual conversion formula is unchanged. There is no security issue visible in the diff.

This commit renames a read-only exchange-rate API from 'currencyrates' to 'listcurrencyrates' and changes the response format from a flat map of millisatoshi-per-currency-unit values to a structured list of source names and BTC prices. It also adds the missing JSON schema and documentation. There is no security fix or vulnerability here; it is a normal API cleanup and documentation improvement.

This commit only adds missing documentation (a JSON schema and manual page references) for an existing RPC command called currencyconvert. It does not change any executable code, network behavior, or security logic. There is no security issue here.

This commit adds a new public command called currencyrate to Core Lightning. It lets users ask the node for the current median exchange rate of one bitcoin into a chosen fiat currency. The change is purely a feature addition: it exposes data that the existing currencyrate plugin already collects, without altering security-sensitive logic such as wallet handling, network parsing, or cryptographic checks.

This commit is a routine internal code cleanup. It replaces hand-built slash-separated datastore key strings with a new helper function, mkdatastorekey, that builds the same keys as a list of separate parts. There is no indication this fixes a security bug; it is a refactoring to make the code simpler and less error-prone.