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

cln-grpc: fix txids encoding in close command

Public commit record

What the developer wrote

Authored by daywalker90

45/100 · Thin
cln-grpc: fix txids encoding in close command

Changelog-None
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
The short version

What changed, and why it matters

This commit fixes how transaction IDs (txids) are encoded when the 'close' command response is sent over the gRPC interface in Core Lightning. Previously, the txids were likely passed through as plain strings instead of being decoded from hex into raw bytes, which could cause the gRPC layer to produce malformed or unexpected data for clients. The fix also updates the code generator so future txid fields are handled correctly in both directions.

Recommended action

Review other gRPC response fields for similar type mismatches, consider replacing unwrap() with proper error handling for hex decoding, and regenerate cln-grpc conversion code to ensure the generator fix is reflected across all txid usages.

Security signals we found

01

Data serialization mismatch in gRPC response field

02

Use of unwrap() on hex decode (panic on malformed input)

03

Generated code fix in msggen to prevent recurrence for txid fields

Risk score

Why this scored 24/100

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