Amber nodes are monitored by CommitWatch. Gray nodes are sampled from authenticated GitHub public commit search and may not represent complete contribution history.
This commit adds a single step to the project's Mac CI workflow that verifies generated documentation files are up to date. It is a build/test hygiene change with no security relevance.
This commit fixes a flaky automated test, not a security issue. The test sometimes received an extra timing-related notification when the machine was slow. The change makes the test tolerate that extra notification by tracking which notifi…
This commit is a routine update to the project's Mac CI (Continuous Integration) workflow. It installs the GNU version of make (called gmake) via Homebrew and uses gmake instead of the older Apple-provided make when building the project in…
This commit fixes a bug in Core Lightning's splicing feature where the fee rate used for splice transactions was accidentally based on the much higher 'unilateral close' fee rate instead of the intended 'opening' fee rate plus a small offs…
Incorrect fee-rate source used for splice transactions (unilateral close rate instead of opening rate)New dedicated splice_feerate helper clamps value to feerate_max to prevent runaway feesBalance safety checks in channeld updated to use max feerate boundary
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 ch…
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 remov…
Behavioral change in monetary parsing: rounding mode changed from nearest to downChangelog labels the change as a fix for user-facing splice commandsTest expectations changed: xfail markers removed, indicating previously failing real behavior
This is a one-line memory leak fix in a rarely-used error path of the splicing plugin. When a splice attempt fails because the peer does not support splicing, a small helper object was allocated against the plugin's long-lived context inst…
This commit turns on a new Lightning protocol feature called 'splicing' by default. Splicing lets users add or remove funds from an existing Lightning channel without closing and reopening it. The change itself is a simple configuration de…
This is a tiny change to the project's build/CI Makefile. It adds the `--text` flag to a `git diff` command that runs during automated checks. This only affects how test failures are displayed when generated documentation files don't match…
This commit fixes a typo in a test file and removes a marker that was causing the test to be expected to fail. The change only affects internal testing code, not the actual Core Lightning software that users run. There is no security issue…
This commit only adds documentation and a JSON schema for an existing 'spliceout' command. No code behavior changes, no bug fixes, and no security-related changes are present.
This commit only adds a new Python client helper and automated tests for an existing 'splice out' Lightning feature. There is no change to the daemon's security-critical code, no bug fix, and no indication of a vulnerability.
This commit adds a new user-facing command called 'spliceout' that makes it simpler to remove funds from a Lightning channel via splicing. It is a feature addition built on top of an existing splicing framework and does not appear to fix a…
This commit only adds documentation for an existing RPC command called splicein. It does not change any executable code, cryptographic logic, network handling, or wallet behavior. There is no security issue here.
This commit only adds a new test for an existing feature and a small Python helper to call that feature. There is no change to the actual Core Lightning server code that handles money or network messages, so it does not create or fix a sec…
This commit adds a new user-facing command called 'splicein' to Core Lightning. It is a convenience wrapper around the existing experimental 'dev-splice' feature, letting users splice additional funds into an existing Lightning channel wit…
This is a small bug-fix in Core Lightning's splicing plugin. The code previously always tried to write a debug log array into a JSON response, even when no debug log existed. The patch adds a check so the log array is only emitted when a d…
NULL pointer guard added around debug log serializationPotential malformed JSON / empty array emission preventedNo explicit security claim in commit message or diff
This change fixes a minor operational bug in Core Lightning's gossip handling. Previously, when a stale channel announcement arrived after a channel was spliced (a process that spends the original funding output), the software treated it a…
Change removes peer connection reset on malformed/stale gossip messageDowngrades warning to trace logBehavior aligns with Lightning spec: ignore stale channel announcements
This commit fixes a rare parsing bug in Core Lightning's splice script feature. When a user typed a channel identifier that happened to start with the same characters as a node public key (02 or 03), the software would first try to interpr…
Input misclassification bug in script parserRare corner case based on identifier prefixNo buffer overflow, use-after-free, or cryptographic flaw visible
This commit simply adds a new 'splice' feerate field to the existing feerates RPC response. It exposes information that was already computed internally so users and API consumers can see what fee rate the node recommends for splicing opera…