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

Rename `starting_htlc_offset` `cur_block_height` in onion building

Public commit record

What the developer wrote

Authored by Matt Corallo

73/100 · Adequate
Rename `starting_htlc_offset` `cur_block_height` in onion building

Now that we are consistently using the
`RouteHop::cltv_expiry_delta` as the last hop's starting CLTV
rather than summing trampoline hops, `starting_htlc_offset` is a
bit confusing - its actually always the current block height. Thus,
here we rename it.
✓ 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 simple variable rename in the code that builds Lightning payment onion payloads. The old name `starting_htlc_offset` was misleading because the value is actually the current block height, so it was renamed to `cur_block_height`. No behavior changed.

Recommended action

No action needed; this is a cosmetic rename with no security or functional impact.

Security signals we found

No strong security signals were identified.

Risk score

Why this scored 15/100

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