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

schemas: make `direction` in `listpeerchannels` a u32

EPb4a9dc51 View source ↗
Public commit record

What the developer wrote

Authored by daywalker90

65/100 · Adequate
schemas: make `direction` in `listpeerchannels` a u32

everywhere else it's a u32 aswell, an `integer` makes it a i64
but possible values are only 0 and 1

Changelog-None
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
The short version

What changed, and why it matters

This commit is a minor API consistency fix. It changes the data type of the `direction` field returned by the `listpeerchannels` command from a signed 64-bit integer (`integer`/`sint64`) to an unsigned 32-bit integer (`u32`/`uint32`). The field only ever holds the values 0 or 1, so this simply aligns it with how the same field is represented in other parts of the API. It is not a security patch and does not fix a vulnerability.

Recommended action

No security action required. Treat as a normal API consistency / code-generation update. Review downstream consumers that may have assumed a signed 64-bit type for `direction` in `listpeerchannels` responses, as the narrower unsigned type could affect strict type checking in client code.

Security signals we found

01

No security-relevant signals detected in the diff.

02

Change is purely a type narrowing / API consistency fix.

03

No input validation, memory safety, or cryptographic changes present.

Risk score

Why this scored 19/100

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

More from Core Lightning

Related watches

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

contrib: add jaonoctus's signing key

This commit simply adds a new person's PGP public-key fingerprint to the list of trusted release signers in two documentation files. It does not change any code, fix any bug, or alter any security behavior of the software itself.

41278b4eby jaonoctus+2−02 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

wallet: fixed timestamps for invented bookkeeper deposits

This is a tiny internal fix to make a bookkeeping migration produce stable event ordering. It changes the timestamp used when creating historical 'deposit' records during a one-time database migration, so the records sort consistently with…

498e5086by daywalker90+2−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 21 AI analysisMessage 85 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

docs: document missing and fix erroneous JSON-RPC error codes

This commit is a documentation-only cleanup of the JSON-RPC command help files. It corrects which numeric error codes are listed for each command so the published schemas match what the software actually returns. No program logic, validati…

Documentation-only change with no executable code modificationsCorrects RPC schema error-code metadata to match actual handler behaviorNo change to input parsing, authorization, cryptography, or network behavior
d1b6963bby daywalker90+204−1224 files
No security note in commit
Open full analysis →Source commit ↗