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

getroutes: deprecate old vaguely named fields.

Public commit record

What the developer wrote

Authored by Rusty Russell

68/100 · Adequate
getroutes: deprecate old vaguely named fields.

Changelog-Deprecated: JSON-RPC: `getroutes` `route` fields `next_node_id`, `amount_msat` and `delay` (use `node_id_out`, `amount_in_msat` and `cltv_in`).
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
✓ 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 routine API cleanup, not a security fix. It renames three fields in the getroutes JSON-RPC response to clearer names and marks the old names as deprecated. The old fields are still emitted for backward compatibility unless a user opts into strict deprecation handling. There is no vulnerability being patched here.

Recommended action

No security action required. Developers using getroutes should plan to migrate from next_node_id, amount_msat, and delay to node_id_out, amount_in_msat, and cltv_in before the deprecated fields are removed in v27.06.

Security signals we found

No strong security signals were identified.

Risk score

Why this scored 21/100

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