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

clusterlin: replace cluster linearization with SFL (feature)

Public commit record

What the developer wrote

Authored by Pieter Wuille

83/100 · Strong
clusterlin: replace cluster linearization with SFL (feature)

This replaces the existing LIMO linearization algorithm (which internally uses
ancestor set finding and candidate set finding) with the much more performant
spanning-forest linearization algorithm.

This removes the old candidate-set search algorithm, and several of its tests,
benchmarks, and needed utility code.

The worst case time per cost is similar to the previous algorithm, so
ACCEPTABLE_ITERS is unchanged.
✓ 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 swaps out Bitcoin Core's old mempool cluster linearization algorithm (LIMO) for a new one called SFL (spanning-forest linearization). The change is described as a performance improvement, not a security fix. It removes a lot of old search-based code and tests, and temporarily relaxes one test assertion because the new algorithm does not yet guarantee the smallest possible number of chunks even when it finds an optimal ordering. The production code now always runs an extra post-processing step to keep chunks connected.

Recommended action

Treat as a routine refactor/feature commit. Reviewers should verify that the new SFL algorithm preserves the same optimality/diagram guarantees as the old one, that the relaxed test assertions are re-enabled in a follow-up, and that the always-on PostLinearize step does not introduce performance regressions. No immediate security response is indicated.

Security signals we found

01

Algorithm replacement in mempool transaction ordering

02

Temporary relaxation of test assertion for minimal chunks

03

PostLinearize now always invoked to preserve connected chunks

04

No explicit security relevance stated by vendor

05

No CVE or advisory references present

Risk score

Why this scored 18/100

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