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

Use zero splice min-depth in zero-conf splice reorg test

Public commit record

What the developer wrote

Authored by Matt Corallo

83/100 · Strong
Use zero splice min-depth in zero-conf splice reorg test

`test_zero_conf_splice_stays_locked_when_unconfirmed` relies on a
zero-conf splice sending `splice_locked` as soon as it is signed. Since
splices on zero-conf channels now wait for `inbound_splice_min_depth`
and `outbound_splice_min_depth` (both defaulting to 6), the test's
splice no longer locked at signing and it failed waiting for the
`splice_locked` message.

The test landed concurrently with the min-depth knobs, so it missed
the update applied to the other zero-conf splice tests. Set both knobs
to 0 as those tests do.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
The short version

What changed, and why it matters

This commit only fixes a test that was failing because of a recent unrelated change. It does not change any production code or fix a security issue. The test now explicitly sets two new configuration knobs to zero so the test scenario behaves as originally intended.

Recommended action

No security action required. This is a test-only fix.

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.