EP
← All projectsElements Project

Core Lightning

Modular C implementation of the Lightning Network protocol and node stack.

BitcoinLightning NetworkNormal
Repository coverage

1855 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

158security candidates263second-pass queue639AI analyses
145commits · 30 days
227commits · 60 days
805commits · 180 days
1851commits · 365 days
Backfill bands
Aug 5 → Feb 61049 seen37 candidatesComplete
Feb 6 → Jun 6579 seen10 candidatesComplete
Jun 6 → Jul 678 seen1 candidatesComplete
Jul 6 → Aug 5147 seen16 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

70/100 average clarity
431Strong · 80–100
1164Adequate · 60–79
231Thin · 40–59
29Opaque · 0–39
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
dovgopoly1502164
Rusty Russell95873253072
Sangbida Chaudhuri1473175066
Dusty Daemon771317066
ShahanaFarooqui931034063
daywalker9090549062
Níckolas Goline40540076
Lagrang376438069
Christian Decker3647072
Vincenzo Palazzo834080
Chandra Pratap56250082
ekzyis222063
Analysis record

Published AI watches

Last scanned 48 minutes ago

Informational 15 AI analysisMessage 65 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

Revert "doc: require Homebrew GNU make and gpatch on macOS"

This commit is a simple documentation revert. It undoes a previous change that told macOS users to install GNU make and GNU patch from Homebrew and to put those tools first in their command path. The reverted instructions now omit gpatch a…

0cfa949fby Sangbida Chaudhuri+4−81 file
No security note in commit
Informational 15 AI analysisMessage 75 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

Revert "tests: drop obsolete x-prefix in compacter-slow.sh"

This commit re-adds an old-style 'x' prefix to a string comparison in a test helper script. It is a test-only change with no effect on the actual Core Lightning node software, user funds, network behavior, or security. The change simply re…

116fd7cdby Sangbida Chaudhuri+1−11 file
No security note in commit
Informational 15 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

doc: require Homebrew GNU make and gpatch on macOS

This commit only updates macOS installation instructions in the documentation. It tells macOS users to install newer GNU versions of 'make' and 'patch' from Homebrew because Apple's built-in tools are too old for building and running sourc…

d3ff1474by Sangbida Chaudhuri+8−41 file
No security note in commit
Informational 15 AI analysisMessage 83 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

tests: drop obsolete x-prefix in compacter-slow.sh

This commit is a trivial shell script cleanup. It removes an old-fashioned 'x' prefix from a string comparison in a test helper script so that a newer version of the Shellcheck linter stops warning about it. The change does not alter progr…

474c272aby Sangbida Chaudhuri+1−11 file
No security note in commit
Informational 18 AI analysisMessage 65 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

common: hoist amount+currency parsing into common code.

This commit moves existing code that parses payment amounts (Bitcoin millisatoshis, 'any' amount, or fiat currency amounts) from one plugin file into a shared library so it can be reused by a future feature. It is a code refactoring with n…

Refactoring of amount-parsing code into a shared helperAddition of explicit u64 overflow guards (mul_overflows_u64, add_overflows_u64) in the new common codeNo change to wire protocol or RPC interface semantics
e0f86c17by Rusty Russell+112−723 files
No security note in commit
Informational 17 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

lightningd: internal cleanups since all non-command JSON IDs are strings.

This is a routine internal cleanup commit in Core Lightning. It removes an unused helper function and simplifies how JSON-RPC request IDs are stored and formatted, since the project now always uses string IDs for non-command JSON traffic. …

No security-relevant keywords in commit title or messageNo CVE, advisory, or bug reference presentChanges are refactor/cleanup in nature
a70ae963by Rusty Russell+25−378 files
No security note in commit
Informational 15 AI analysisMessage 65 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

common: hoist hash_str helper into its own header.

This commit is a routine code cleanup: it moves a small string-hashing helper function into a shared header file so it can be reused without being copied and pasted. There is no change to behavior, no bug fix, and no security relevance.

581bbb1fby Rusty Russell+16−176 files
No security note in commit
Informational 23 AI analysisMessage 65 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

downgrade: we need to remove "impressions" from askrene datastore when downgrading to v26.06.

This is a database downgrade helper fix, not a live network vulnerability. Core Lightning's downgrade tool previously failed to strip out new 'channel impression' records when rolling a database back to version v26.06. The patch teaches th…

Database downgrade path could leave incompatible records in older schemaOffline tool only; no remote or on-chain triggerFix prevents potential node startup failure after version rollback
4d926285by Rusty Russell+43−111 file
No security note in commit
Low 31 AI analysisMessage 68 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

downgrade tool: fix invalid memory bug

This commit fixes a typo in a database downgrade helper tool. The bug caused the tool to pass a negative number (turned into a huge positive size) when copying data, which led to an out-of-memory (OOM) error. The fix swaps two variable nam…

Integer underflow / negative-to-size_t wrap leading to excessive allocationOut-of-memory crash in maintenance toolMemory corruption potential if allocation somehow succeeded
42995326by Lagrang3+8−81 file
No security note in commit
Informational 24 AI analysisMessage 65 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

xpay: actually tell askrene when a payment succeeded.

This commit fixes a bookkeeping bug in Core Lightning's xpay plugin. Previously, when a payment succeeded, xpay did not tell the askrene routing-helper that the route worked. As a result, askrene kept stale or overly pessimistic ideas abou…

Missing success feedback to routing layer can degrade payment reliabilityStale negative impressions may bias future path selection toward worse or failing routesNo direct funds-loss primitive is introduced or fixed
a66fabd4by Rusty Russell+40−02 files
No security note in commit
Low 49 AI analysisMessage 58 · Thin
EP Elements ProjectCore Lightning BitcoinLightning Network

askrene: correctly order constraints.

This commit fixes a bug in Core Lightning's routing helper (askrene) where two kinds of channel information—hard limits called 'constraints' and usage estimates called 'impressions'—were being applied in the wrong order. Because impression…

Routing decision bug caused by incorrect ordering of time-relative channel statePotential payment failure or acceptance of an over-capacity routeRegression test added demonstrating incorrect route acceptance before fix
4b6fe4a1by Rusty Russell+211−1182 files
No security note in commit
Low 35 AI analysisMessage 68 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

askrene: don't leak channel intel entries

This commit fixes a memory leak in the askrene plugin of Core Lightning. When individual channel intelligence entries were deleted, the code removed the entry from its array but forgot to free two internal pointers (impression and constrai…

Memory leak in plugin data structure cleanupMissing deallocation of nested pointers before array removalFix located in routing/intelligence plugin (askrene)
8891f414by Lagrang3+5−01 file
No security note in commit
Informational 15 AI analysisMessage 70 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

xpay: tests should expect the new error messages

This commit only updates test files so that automated checks expect slightly different error wording from the xpay payment command. It does not change any production code, so it cannot introduce a security vulnerability or fix one on its o…

0b67601fby Lagrang3+24−32 files
No security note in commit
Low 43 AI analysisMessage 65 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

offers: limit invoices to 10 minutes for recurring offers in other currencies.

This change tightens the lifetime of recurring invoices priced in foreign currencies (like USD) to 10 minutes by default, and refreshes them with current exchange rates when they expire. Previously, such invoices could remain valid for the…

Fixes stale exchange-rate exposure for currency-denominated recurring invoicesAdds configurable expiry cap for recurring currency invoicesDistinguishes user-cancellation (0s expiry) from natural expiry to avoid misleading errors
446312cfby Rusty Russell+134−148 files
No security note in commit
Low 45 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

offers: limit expiry to offer limit, or 10 minutes with currency conversion.

This commit tightens the expiration time on invoices created from BOLT12 offers. Previously, all such invoices defaulted to a 2-hour payment window. Now, if the offer has an absolute expiry, the invoice expires when the offer expires; and …

BOLT12 invoice expiry now bounded by offer absolute expiryCurrency-converted invoices use short expiry to limit exchange-rate exposureNew regression test added for expiry behavior
a6cf4915by Rusty Russell+55−22 files
No security note in commit
Low 29 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

fetchinvoice: don't bother with checking recurrence timing.

This commit removes local timing checks in Core Lightning's fetchinvoice plugin for recurring payments. Instead of the plugin refusing too-early or too-late invoice requests, it now lets the remote node decide and report back. The change i…

Removal of local input-validation checks for recurring invoice requestsReliance on remote-party enforcement for recurrence period limits and pay windowsTest expectations changed from local rejection to remote failure messages
3e49d908by Rusty Russell+2−682 files
No security note in commit
Low 32 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

lightningd: don't do previous invoice checking in createinvoicerequest.

This commit removes a local sanity check in Core Lightning's experimental 'createinvoicerequest' command. Previously, when creating a recurring invoice request, the code looked up past payments by label to verify the previous recurrence wa…

Removal of local payment-state validation for recurring invoice requestsParameter rename from recurrence_label to label in internal RPC callsTest expectations changed from local 'previous invoice has not been paid' errors to remote failure messages
4348d8acby Rusty Russell+5−1224 files
No security note in commit
Low 35 AI analysisMessage 65 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

fetchinvoice: handle weird labels in recurrence_label parameter.

This commit fixes how the fetchinvoice plugin handles user-supplied labels that contain special characters such as backslashes, quotes, tabs, and newlines. Previously these labels were passed as raw strings, which could cause JSON encoding…

JSON injection / improper escaping of user-controlled input passed between RPC componentsPotential mismatch between label parsing and label serialization leading to functional failures or unexpected behaviorFix is narrowly scoped to a single plugin and parameter
d7f87f2dby Rusty Russell+37−102 files
No security note in commit
Informational 15 AI analysisMessage 70 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

Add unit tests for str_to_u64

This commit only adds a new automated test file that checks how a helper function (str_to_u64) converts text strings to unsigned 64-bit integers. It does not change any production code, so it cannot by itself introduce a security vulnerabi…

dddb455dby Lagrang3+203−01 file
No security note in commit
Informational 15 AI analysisMessage 78 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

pytest: add tests for what we want askrene to do.

This commit only adds a new pytest test file. It does not change any production code. The test describes desired future behavior for the askrene routing module's error messages when a payment source or destination lacks enough channel capa…

518620aeby Rusty Russell+67−01 file
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Lower-prioritylightningd: use scriptpubkey and blockdepth watches instead of tx watches for dual funding.by Rusty Russell · 53d0de44 · Mar 22, 2026 · 1 fileMessage 65 · AdequateTriage 0Details
Commit message · Rusty Russell

lightningd: use scriptpubkey and blockdepth watches instead of tx watches for dual funding.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Lower-priorityCCAN: import version with htable_lock.by Rusty Russell · 658eb771 · Mar 22, 2026 · 4 filesMessage 60 · AdequateTriage 0Details
Commit message · Rusty Russell

CCAN: import version with htable_lock.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Lower-prioritylightningd: use scriptpubkey watch and block depth watch for splicing.by Rusty Russell · c4beb2a7 · Mar 22, 2026 · 1 fileMessage 65 · AdequateTriage 0Details
Commit message · Rusty Russell

lightningd: use scriptpubkey watch and block depth watch for splicing.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Lower-prioritysplice: Add easy spliceout commandby Dusty Daemon · d9bf9110 · Mar 22, 2026 · 2 filesMessage 68 · AdequateTriage 0Details
Commit message · Dusty Daemon

splice: Add easy spliceout command

Adds a RPC command for easily splicing out. Built on top of the splice script framework.

Changelog-Added: New command `spliceout` for easily splicing out of channels

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritysplice: Add test for easy spliceout commandby Dusty Daemon · bf15842f · Mar 22, 2026 · 2 filesMessage 55 · ThinTriage 0Details
Commit message · Dusty Daemon

splice: Add test for easy spliceout command

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-prioritysplice: Add docs for easy spliceout commandby Dusty Daemon · f3dd81fd · Mar 22, 2026 · 4 filesMessage 45 · ThinTriage 0Details
Commit message · Dusty Daemon

splice: Add docs for easy spliceout command

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityAdd splicein commandby Dusty Daemon · 29119d50 · Mar 22, 2026 · 2 filesMessage 51 · ThinTriage 0Details
Commit message · Dusty Daemon

Add splicein command

splicein is the convience method for splicing in using the splice script system.

Changelog-Added: New command `splicein` allows for convenient splicing funds into a channel

51/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides detailed explanatory context
Lower-prioritysplice: Add documentation for spliceinby Dusty Daemon · 3ef72bf4 · Mar 22, 2026 · 4 filesMessage 45 · ThinTriage 0Details
Commit message · Dusty Daemon

splice: Add documentation for splicein

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-prioritysplice: Add splicein testby Dusty Daemon · 791e412e · Mar 22, 2026 · 2 filesMessage 45 · ThinTriage 0Details
Commit message · Dusty Daemon

splice: Add splicein test

Tests the splicein command

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Mentions testing or verification! No meaningful explanatory body
Lower-prioritysplice script: Switch to splice feerateby Dusty Daemon · 26efb301 · Mar 20, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Dusty Daemon

splice script: Switch to splice feerate

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-prioritychanneld: Inform channeld about opening feerateby Dusty Daemon · 6f5fb632 · Mar 20, 2026 · 4 filesMessage 68 · AdequateTriage 0Details
Commit message · Dusty Daemon

channeld: Inform channeld about opening feerate

Since channeld handles splicing, it makes sense that it knows the opening feerate now. This is needed for rounding out splice script errors and logging.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritysplice: Add and improve loggingby Dusty Daemon · d23b80a1 · Mar 20, 2026 · 3 filesMessage 60 · AdequateTriage 0Details
Commit message · Dusty Daemon

splice: Add and improve logging

Add lots of logging to help debug and develop splice related work

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Lower-prioritysplice script: Helper functions for dynamic calcsby Dusty Daemon · 13e2a8f7 · Mar 20, 2026 · 1 fileMessage 60 · AdequateTriage 0Details
Commit message · Dusty Daemon

splice script: Helper functions for dynamic calcs

Implement some helper functions to make implemetning dynamic wallet and fee amounts easier.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Lower-prioritysplice: test mutli-channel splice script and feesby Dusty Daemon · bb15b37f · Mar 20, 2026 · 1 fileMessage 70 · AdequateTriage 0Details
Commit message · Dusty Daemon

splice: test mutli-channel splice script and fees

Adds tests for multi channel wallet scripts and complex situations involving difficult fee calculations.

70/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification
Security candidategossip: Don’t reset channel on stale annoncementby Dusty Daemon · 404bb5a0 · Mar 20, 2026 · 1 fileMessage 78 · AdequateInformational 20Details
Commit message · Dusty Daemon

gossip: Don’t reset channel on stale annoncement

Splicing can create stale announcements where the original funding output gets spent creating spruious “channel_announcement: no unspent txout” warnings.

This happens particuarlly often with agressive splice tests in CI, so we downgrade this from a warning to a log message.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
update trust
AI analysis · Informational 20/100

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 as a warning and reset the peer connection. The patch downgrades this to a simple log/trace message and ignores the stale announcement, which matches the Lightning specification. This is a stability improvement, not a security vulnerability fix.

Lower-priorityamount: Add decimal format for msatsby Dusty Daemon · 934def8d · Mar 20, 2026 · 3 filesMessage 68 · AdequateTriage 0Details
Commit message · Dusty Daemon

amount: Add decimal format for msats

In splicing logs we’re often outputting msat values next to sat values, making understanding the logs difficult.

Adding a way to output msats as sats with a decimal makes these logs much easier to read.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritysplice script: Improve weight guess calculationby Dusty Daemon · 252dd6fd · Mar 20, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Dusty Daemon

splice script: Improve weight guess calculation

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-prioritysplice: multi channel stfu bugfixby Dusty Daemon · 66b1eed9 · Mar 20, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · Dusty Daemon

splice: multi channel stfu bugfix

When executing splices with many channels at once the `channel_ids` and `results` arrays could be reallocted via `tal_arr_remove` and `tal_arr_expand`.

Since these values are shared across multiple `splice_command` objects, when these functions reallocated the arrays the other `splice_command` would be referencing an invalid pointer.

The solution is to make an explicit shared object `stfu_req_info` that is shared amoung the `splice_command`s and holds pointers to the arrays so they can mutate.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritysplice script: Zero out wallet fund requestsby Dusty Daemon · fde4a1ce · Mar 20, 2026 · 2 filesMessage 68 · AdequateTriage 0Details
Commit message · Dusty Daemon

splice script: Zero out wallet fund requests

To prepare for dynamic wallet funding abilities, we pre-process the wallet withdrawls and move them to `needed_funds`. These wallet withdrawl amounts are zero’d out and will have their total withdrawl amount caluclated later on.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritysplice: Update `tx_abort` for mulitple splicesby Dusty Daemon · 52ed23f0 · Mar 20, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · Dusty Daemon

splice: Update `tx_abort` for mulitple splices

If the channel has multiple splice candidates pending at once, `tx_abort` needs to know which candidate is being aborted.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritysplice script: Turn “wallet -> *” into “wallet -> 100%”by Dusty Daemon · 8843e8c2 · Mar 20, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · Dusty Daemon

splice script: Turn “wallet -> *” into “wallet -> 100%”

Treat the `*` as if it were `100%` for wallets.

100% is a special case that means “100% of needed funds” not “100% of wallet funds.” since taking out all of the wallet’s inputs is wasteful.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityamount: Can add sat convenience methodby Dusty Daemon · bb1674f3 · Mar 20, 2026 · 2 filesMessage 60 · AdequateTriage 0Details
Commit message · Dusty Daemon

amount: Can add sat convenience method

Just a convenient method for checking if a given signed sat value can be subtracted from an msat value.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Lower-prioritysplice script: Allow `out_ppm` for walletby Dusty Daemon · 434ef5a7 · Mar 20, 2026 · 1 fileMessage 60 · AdequateTriage 0Details
Commit message · Dusty Daemon

splice script: Allow `out_ppm` for wallet

To help manage state around dynamic wallets, we allow `out_ppm` to stay on even after its result is calculated.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Security candidatesplice: Fix weight calculations & use opening feerateby Dusty Daemon · 46984883 · Mar 20, 2026 · 6 filesMessage 73 · AdequateLow 42Details
Commit message · Dusty Daemon

splice: Fix weight calculations & use opening feerate

Here we update `psbt_input_get_weight` to allow the caller to specify what kind of input size estimation they would like. Before it was just “zero witness bytes” which we now move to the default behavior and add an assumption option for P2WSH -> 2of2 multisig which is what we typically see in splicing.

At the same time we move channeld over to using the opening feerate estimation instead of the less useful “max feerate.” We make splice script use this same feerate.

After auditing the feerates for these two places against each other and the actually created transaction, we implement some fixes making them all match.

While we’re here, we add relevant debug log messages.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 42/100

This commit fixes how Core Lightning estimates the size (and therefore the required mining fee) of Bitcoin transactions used in channel splicing. Before, the code underestimated input weights for common 2-of-2 multisig splicing inputs and used a less useful 'maximum feerate' as a safety cap. The patch adds better size-estimation options, switches the safety cap to the 'opening feerate,' and aligns the math between the different components that negotiate a splice. The main risk is that incorrect fee math could cause a splice transaction to be rejected by the network (too low fee) or to overpay/underpay, potentially disrupting channel operations or funds movement.

Lower-prioritychanneld: Add new feerate type ‘splice’by Dusty Daemon · 3728c61a · Mar 20, 2026 · 4 filesMessage 60 · AdequateTriage 0Details
Commit message · Dusty Daemon

channeld: Add new feerate type ‘splice’

This new feerate gives us more careful control of what feerate splices should be at.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body