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

common/coin_mvt: add struct mvt_account_id to separate channels from others.

Public commit record

What the developer wrote

Authored by Rusty Russell

73/100 · Adequate
common/coin_mvt: add struct mvt_account_id to separate channels from others.

This means we can keep a pointer to the channel directly, *or* a string.
This avoids gratuitous formatting (on creation) and lookups (later).

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 is a code-quality refactor in Core Lightning's internal accounting system. It replaces formatted channel ID strings with direct pointers to channel objects, and introduces a small helper structure that can hold either a channel pointer or an alternative account name. The change removes unnecessary string formatting and lookups, and updates the wire serialization format for on-chain coin movement records. There is no indication of a security vulnerability being fixed or introduced.

Recommended action

No security action required. Treat as normal code maintenance. Reviewers may want to confirm that the new wire format change is backward-compatible for the onchaind/lightningd interface, and that the empty-string sentinel for 'this channel' is handled consistently.

Security signals we found

01

Refactor only: no security-relevant logic changes observed

02

Wire format change for chain coin movements (account_name now always sent as wirestring, originating_acct removed from wire)

03

Assertions added in constructors and wire send path

04

No bounds checks, memory allocations, or cryptographic operations changed in a security-sensitive way

Risk score

Why this scored 17/100

Our methodology →
Potential impact 2/30
Exploitability 1/25
Stealth signal 1/15
Affected reach 2/15
Confidence 8/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.