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

Require closed channels migration before starting (#3198)

Public commit record

What the developer wrote

Authored by Bastien Teinturier

81/100 · Strong
Require closed channels migration before starting (#3198)

We require closed channels to be migrated to the closed channels table
introduced in #3170 before starting `eclair`. This ensures that we
will not lose channel data when removing support for non-anchor channels
in the next release.

Node operators will have to:

- run the v0.13.0 release to migrate their channel data to v5
- run the v0.13.1 release to migrate their closed channels

Afterwards, they'll be able to update to the (future) v0.14.x release
once all of their pre-anchor channels have been closed.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This commit changes Eclair's database startup checks so that the node refuses to start unless the operator has already run the v0.13.0 and v0.13.1 releases to migrate channel data. The migration code that used to run automatically when Eclair started has been removed from the startup path and replaced with a hard requirement. This is a defensive, operational-safety change, not a remotely exploitable vulnerability fix. It prevents accidental data loss for operators who skip intermediate releases, but it does not patch a security bug that an attacker could abuse.

Recommended action

No immediate security patch is required. Node operators should verify their channels DB version before upgrading past v0.13.x: SQLite must be at version 8 and PostgreSQL at version 12. If not, run v0.13.0 then v0.13.1 first to complete migrations. Developers should ensure release notes clearly state this two-step upgrade path and consider preserving offline migration tooling for operators who cannot run the intermediate releases.

Security signals we found

01

Database version gating added at startup

02

Automatic closed-channel migration code removed from startup path

03

Hard failure on missing migration to prevent data loss

04

Operational safety guard, not an exploit patch

Risk score

Why this scored 26/100

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