AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 20 Bitcoin

lightningd: save funding_psbt in channel, database.

Public commit record

What the developer wrote

Authored by Rusty Russell

73/100 · Adequate
lightningd: save funding_psbt in channel, database.

Interestingly, @niftynei added a funding_psbt column to the db in 2020,
but we don't use it (it was removed early 2021 with the "inflight"
architecture). So we don't need to add a new column, just plumb it
back in.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit restores the use of an existing database column called funding_psbt in Core Lightning. It stores the unsigned Bitcoin transaction (PSBT) used to fund a Lightning channel in the channel record and database. The change itself is a data plumbing fix, not an obvious security patch. There is no direct evidence in the commit that it fixes an active vulnerability, but storing sensitive transaction data securely matters because the PSBT contains details about the funds being committed.

Recommended action

Review whether persisted funding PSBTs contain any private key material, non-finalized signatures, or other sensitive data that should be encrypted at rest. Verify that db_col_psbt and db_bind_psbt handle NULL and malformed values safely. Consider whether this change is a prerequisite for a later security fix and monitor related follow-up commits.

Security signals we found

01

Restores persistence of unsigned funding PSBT in database column

02

Adds funding_psbt to channel, closed_channel, and funding_channel structs

03

Updates wallet save/load paths for active and closed channels

04

No explicit security framing or CVE reference in commit message

05

No input validation or memory-safety changes visible in diff

Risk score

Why this scored 20/100

Our methodology →
Potential impact 3/30
Exploitability 2/25
Stealth signal 2/15
Affected reach 3/15
Confidence 7/10
Evidence quality 3/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.